Skip to content
Server Security Center
KEVhigh7.5

CVE-2024-38178: Microsoft Windows Scripting Engine Memory Corruption

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2024-08-13.

CVSS v3.1 (CVE record)
7.5
high
EPSS (exploit probability, 30 days)
41%
higher than 98.7% of all CVEs
Added to CISA KEV
2024-08-13
US federal due date 2024-09-03
Automatable (CISA SSVC)
no
technical impact: total

CVE-2024-38178 explained

CVE-2024-38178 is a memory corruption vulnerability in the Microsoft Windows Scripting Engine. It is a type confusion flaw that allows an unauthenticated attacker to start remote code execution through a specially crafted URL. CISA lists it as known to be exploited, so patching affected Windows client and server versions should be a priority.

Impact

An unauthenticated attacker can achieve remote code execution over the network, with high impact on confidentiality, integrity and availability. User interaction is required and attack complexity is high. CISA's SSVC assessment rates the vulnerability as not automatable, with total technical impact, meaning total control of the affected component. Attackers are known to use this vulnerability. Whether it is used in ransomware campaigns is unknown.

Who is affected

The CVE record lists Windows 10 Version 1809, 21H2 and 22H2; Windows 11 versions 21H2, 22H2, 22H3, 23H2 and 24H2; Windows Server 2019, Windows Server 2022 and Windows Server 2022, 23H2 Edition, including Server Core installations. Fixed builds include 10.0.17763.6189 (1809/Server 2019), 10.0.19044.4780, 10.0.19045.4780, 10.0.20348.2655, 10.0.22000.3147, 10.0.22621.4037, 10.0.22631.4037, 10.0.25398.1085 and 10.0.26100.1457. Further products are listed on this page.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft Windows Scripting Engine contains a memory corruption vulnerability that allows unauthenticated attacker to initiate remote code execution via a specially crafted URL.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.1457
    Fixed in
    • 10.0.26100.1457
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.6189
    Fixed in
    • 10.0.17763.6189
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.6189
    Fixed in
    • 10.0.17763.6189
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.6189
    Fixed in
    • 10.0.17763.6189
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.2655
    Fixed in
    • 10.0.20348.2655
  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    • < 10.0.22000.3147
    Fixed in
    • 10.0.22000.3147
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.4780
    Fixed in
    • 10.0.19044.4780
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.4037
    Fixed in
    • 10.0.22621.4037
  • Microsoft Windows 10 Version 22H2x64, ARM64, 32-bit
    Affected
    • < 10.0.19045.4780
    Fixed in
    • 10.0.19045.4780
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.4037
    Fixed in
    • 10.0.22631.4037
Show 8 more products
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.4037
    Fixed in
    • 10.0.22631.4037
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1085
    Fixed in
    • 10.0.25398.1085
  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.20751
    Fixed in
    • 10.0.10240.20751
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.7259
    Fixed in
    • 10.0.14393.7259
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.7259
    Fixed in
    • 10.0.14393.7259
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.7259
    Fixed in
    • 10.0.14393.7259
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22134
    Fixed in
    • 6.3.9600.22134
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22134
    Fixed in
    • 6.3.9600.22134

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 11 Version 24H2: 10.0.26100.1457
    • Microsoft Windows 10 Version 1809: 10.0.17763.6189
    • Microsoft Windows Server 2019: 10.0.17763.6189
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.6189
    • Microsoft Windows Server 2022: 10.0.20348.2655
    • Microsoft Windows 11 version 21H2: 10.0.22000.3147
    Fixed versions for 12 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38178
  • CISA's deadline for US federal agencies: 2024-09-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to the fixed build listed for its Windows version.
  2. Prioritize internet-facing systems and user workstations, since exploitation involves a user opening a crafted URL.
  3. Follow the Microsoft advisory; per CISA, apply vendor mitigations or discontinue use if mitigations are unavailable.
  4. Verify the installed build number on each host after patching.
  5. Check systems that were unpatched for signs of compromise, given confirmed exploitation.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')

Questions about CVE-2024-38178

Is CVE-2024-38178 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-08-13, with a US federal due date of 2024-09-03. Known ransomware use is listed as unknown.
Does an attacker need credentials?
No. The attacker does not need to be authenticated, but user interaction is required and attack complexity is high.
Which build fixes Windows Server 2022?
Windows Server 2022 is fixed in build 10.0.20348.2655. Windows Server 2022, 23H2 Edition (Server Core installation) is fixed in 10.0.25398.1085.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.