Skip to content
Server Security Center
KEVhigh7.8

CVE-2024-43572: Microsoft Windows Management Console Remote Code Execution

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

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
67%
higher than 99.3% of all CVEs
Added to CISA KEV
2024-10-08
US federal due date 2024-10-29
Automatable (CISA SSVC)
no
technical impact: total

CVE-2024-43572 explained

CVE-2024-43572 is a remote code execution vulnerability in the Microsoft Windows Management Console, affecting a wide range of Windows client and server versions. CISA lists it as known to be exploited by attackers, and successful exploitation can give total control of the affected component.

Impact

An attacker who succeeds can run code with high impact on confidentiality, integrity and availability. The CVSS vector shows a local attack vector, low complexity and no privileges required, but user interaction is needed. A user must take an action for the attack to work. CISA rates technical impact as total and the attack as not automatable. Attackers are known to use this vulnerability. Ransomware use is listed as unknown.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 21H2 and 22H2. It also lists Windows 11 versions 21H2, 22H2, 22H3, 23H2 and 24H2, plus Windows Server 2008 Service Pack 2 and Windows Server 2008 R2 Service Pack 1. Fixed builds include 10.0.19045.5011 (Windows 10 22H2), 10.0.22631.4317 (Windows 11 23H2), 10.0.26100.2033 (Windows 11 24H2) and 6.1.7601.27366 (Server 2008 R2 SP1). 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 Management Console contains unspecified vulnerability that allows for remote code execution.

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 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.20796
    Fixed in
    • 10.0.10240.20796
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.7428
    Fixed in
    • 10.0.14393.7428
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.6414
    Fixed in
    • 10.0.17763.6414
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.5011
    Fixed in
    • 10.0.19044.5011
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.5011
    Fixed in
    • 10.0.19045.5011
  • Microsoft Windows 11 version 21H2ARM64, x64
    Affected
    • < 10.0.22000.3260
    Fixed in
    • 10.0.22000.3260
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.4317
    Fixed in
    • 10.0.22621.4317
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.4317
    Fixed in
    • 10.0.22631.4317
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.4317
    Fixed in
    • 10.0.22631.4317
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.2033
    Fixed in
    • 10.0.26100.2033
Show 14 more products
  • Microsoft Windows Server 2008 Service Pack 2x64, 32-bit
    Affected
    • < 6.0.6003.22918
    Fixed in
    • 6.0.6003.22918
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27366
    Fixed in
    • 6.1.7601.27366
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27366
    Fixed in
    • 6.1.7601.27366
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.22918
    Fixed in
    • 6.0.6003.22918
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25118
    Fixed in
    • 6.2.9200.25118
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25118
    Fixed in
    • 6.2.9200.25118
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22221
    Fixed in
    • 6.3.9600.22221
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22221
    Fixed in
    • 6.3.9600.22221
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.7428
    Fixed in
    • 10.0.14393.7428
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.7428
    Fixed in
    • 10.0.14393.7428
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.6414
    Fixed in
    • 10.0.17763.6414
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.6414
    Fixed in
    • 10.0.17763.6414
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.2762
    Fixed in
    • 10.0.20348.2762
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1189
    Fixed in
    • 10.0.25398.1189

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.20796
    • Microsoft Windows 10 Version 1607: 10.0.14393.7428
    • Microsoft Windows 10 Version 1809: 10.0.17763.6414
    • Microsoft Windows 10 Version 21H2: 10.0.19044.5011
    • Microsoft Windows 10 Version 22H2: 10.0.19045.5011
    • Microsoft Windows 11 version 21H2: 10.0.22000.3260
    Fixed versions for 18 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43572
  • CISA's deadline for US federal agencies: 2024-10-29 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each affected system to the fixed build listed for its Windows version.
  2. Prioritize patching, since CISA lists this vulnerability as known exploited. The US federal due date was 2024-10-29.
  3. Follow the vendor advisory and apply its mitigations. If mitigations are unavailable, discontinue use of the product, per CISA's required action.
  4. Warn users not to open untrusted files, since exploitation requires user interaction.
  5. Review systems for signs of compromise, especially any left unpatched for a long time.

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-707 Improper Neutralization

Questions about CVE-2024-43572

Is CVE-2024-43572 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-10-08, which means attackers are known to use it. Whether it has been used in ransomware campaigns is listed as unknown.
Can it be exploited without user action?
No. The CVSS vector shows that user interaction is required and the attack vector is local. CISA also rates it as not automatable. No privileges are required.
Which update fixes it?
Each affected Windows version has a fixed build in the CVE record. Examples are 10.0.19045.5011 for Windows 10 22H2 and 10.0.26100.2033 for Windows 11 24H2. Check the vendor advisory for the matching update.

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-21. Always confirm with the vendor's or distribution's advisory before patching.