nday
CVE-2024-38178

Scripting Engine Memory Corruption Vulnerability

Microsoft / Windows, Windows 11 Version 24H2, Windows 10 Version 1809, Windows Server 2019, Windows Server 2019 (Server Core installation), Windows Server 2022 +13

Added to CISA KEV on the day of disclosure. nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

type confusion
CWE-843, stated by the CNA microsoft and NVD, republishing [email protected]
network
AV:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C (CVSS 3.1) from the CNA microsoft
no authentication required
PR:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C (CVSS 3.1) from the CNA microsoft
Windows
affected products in the CVE record: Microsoft · Windows, Microsoft · Windows 10 Version 1507, Microsoft · Windows 10 Version 1607, Microsoft · Windows 10 Version 1809, Microsoft · Windows 10 Version 21H2, Microsoft · Windows 10 Version 22H2, Microsoft · Windows 11 Version 23H2, Microsoft · Windows 11 Version 24H2, Microsoft · Windows 11 version 21H2, Microsoft · Windows 11 version 22H2 and 1 moreCPE names NVD's analysts give as vulnerable: o:microsoft:windows_10_1507, o:microsoft:windows_10_1607, o:microsoft:windows_10_1809, o:microsoft:windows_10_21h2, o:microsoft:windows_10_22h2, o:microsoft:windows_11_21h2, o:microsoft:windows_11_22h2, o:microsoft:windows_11_23h2, o:microsoft:windows_11_24h2
Windows Server
affected products in the CVE record: Microsoft · Windows Server 2012 R2, Microsoft · Windows Server 2012 R2 (Server Core installation), Microsoft · Windows Server 2016, Microsoft · Windows Server 2016 (Server Core installation), Microsoft · Windows Server 2019, Microsoft · Windows Server 2019 (Server Core installation), Microsoft · Windows Server 2022, Microsoft · Windows Server 2022, 23H2 Edition (Server Core installation)CPE names NVD's analysts give as vulnerable: o:microsoft:windows_server_2012, o:microsoft:windows_server_2016, o:microsoft:windows_server_2019, o:microsoft:windows_server_2022, o:microsoft:windows_server_2022_23h2
operating system
affected products in the CVE record: Microsoft · Windows, Microsoft · Windows 10 Version 1507, Microsoft · Windows 10 Version 1607, Microsoft · Windows 10 Version 1809, Microsoft · Windows 10 Version 21H2, Microsoft · Windows 10 Version 22H2, Microsoft · Windows 11 Version 23H2, Microsoft · Windows 11 Version 24H2, Microsoft · Windows 11 version 21H2, Microsoft · Windows 11 version 22H2 and 9 moreCPE names NVD's analysts give as vulnerable: o:microsoft:windows_10_1507, o:microsoft:windows_10_1607, o:microsoft:windows_10_1809, o:microsoft:windows_10_21h2, o:microsoft:windows_10_22h2, o:microsoft:windows_11_21h2, o:microsoft:windows_11_22h2, o:microsoft:windows_11_23h2, o:microsoft:windows_11_24h2, o:microsoft:windows_server_2012 and 4 morethe product type of Windows and Windows Server in nday's product registry
stage
KEV
disclosed
cvss
7.5 HIGH v3.1
KEV due date
2024-09-03

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2024-08-13T17:29Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
≤ 2024-08-13, inferred from KEV
KEVKEV
2024-08-13, date only

Summary

Scripting Engine Memory Corruption Vulnerability

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:H
High: success depends on conditions outside the attacker's control, such as gathering details of the target or winning a race
Privileges required PR:N
None: no account or authorization needed
User interaction UI:R
Required: a user must do something, such as open a file or click a link

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C

CVSS 3.1 vector from the CVE record, scored by the CNA microsoft.

Event log

2024-08-13date only, from source
+KEVadded to KEV

CISA added it to the Known Exploited Vulnerabilities catalog, with a remediation deadline of 2024-09-03. Ransomware use: unknown.

src kev · nday , bulk import · raw
{
  "id": 635,
  "type": "kev_added",
  "source": "kev",
  "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
  "occurred_at": "2024-08-13T00:00:00Z",
  "observed_at": "2026-11-12T13:53:00.018191Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cwes": [
      "CWE-843"
    ],
    "notes": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38178; https://nvd.nist.gov/vuln/detail/CVE-2024-38178",
    "product": "Windows",
    "due_date": "2024-09-03",
    "precision": "day",
    "date_added": "2024-08-13",
    "vendor_project": "Microsoft",
    "forensic_triage": "No",
    "required_action": "Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.",
    "vulnerability_name": "Microsoft Windows Scripting Engine Memory Corruption Vulnerability",
    "known_ransomware_campaign_use": "Unknown"
  }
}
≤ 2024-08-13inferred, no direct source
~ITWexploited in the wild

No source says when exploitation began. A KEV listing means it was already happening, so only an upper bound is known. CISA's SSVC assessment rates exploitation as active.

based on kev and CISA's assessment in cvelist

+DISdisclosed

CVE record published by microsoft. CVSS 7.5, high. CISA's SSVC assessment rates exploitation as active.

src cvelist · nday , bulk import · raw
{
  "id": 17458,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2024-38178",
  "occurred_at": "2024-08-13T17:29:50.491Z",
  "observed_at": "2026-11-12T15:01:53.938848Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "kev": {
      "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-38178",
      "date_added": "2024-08-13"
    },
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C",
      "version": "3.1",
      "base_score": 7.5,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2024-08-14T13:20:41.134913Z",
      "automatable": "no",
      "exploitation": "active",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2024-08-13T17:29:50.491Z",
    "assigner_short_name": "microsoft"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.