dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 29 Oct 2024.
Windows 10 1507Operating system · Microsoft

CVE-2024-43572

HIGH · 7.8 CVSS v3.1 Published 2024-10-08
Fix available
A fix is available. Upgrade to 10.0.10240.20796 / 10.0.14393.7428 or later.
See remediation →
97/100
Remediation priority · Urgent
In the wild High EPSS No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Microsoft Management Console Remote Code Execution Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

CVE-2024-43572 is a remote code execution vulnerability in Microsoft Management Console (MMC), a Windows system administration tool. The CVSS 7.8 score indicates a locally exploitable high-severity flaw that could allow an attacker to execute arbitrary code in the context of the current user.

MitigationApply the Microsoft security update for CVE-2024-43572 immediately once released, as it addresses the RCE vulnerability in MMC. Prioritize workstations and servers where MMC is frequently used.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20796
Windows 10 1607Operating system
Affected:< 10.0.14393.7428
Windows 10 1809Operating system
Affected:< 10.0.17763.6414
Windows 10 21h2Operating system
Affected:< 10.0.19044.5011
Windows 10 22h2Operating system
Affected:< 10.0.19045.5011
Windows 11 21h2Operating system
Affected:< 10.0.22000.3260
Windows 11 22h2Operating system
Affected:< 10.0.22621.4317
Windows 11 23h2Operating system
Affected:< 10.0.22631.4317

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version and build number
    Open Command Prompt and run 'winver' or run 'ver' to display the version string, or use PowerShell with '[System.Environment]::OSVersion.Version'
    Affected if The displayed version matches one of the affected Windows versions (10 or 11) and the build number is lower than the fixed build for that version
  2. Identify exact OS build via systeminfo
    Run 'systeminfo' in Command Prompt and locate the OS Name and OS Version / Build lines, or run 'Get-ComputerInfo' in PowerShell to retrieve WindowsVersion and OsVersion
    Affected if The build number (for example, 19045 for Windows 10 22h2) is below the corresponding threshold in the affected versions list
  3. Confirm MMC executable presence
    Verify mmc.exe exists in the system by running 'where mmc' in Command Prompt or checking for C:\Windows\System32\mmc.exe
    Affected if MMC is present on the system and the Windows version/build falls within the affected range

System is affected if running any Windows 10 or Windows 11 version where the installed build number is lower than the specific patched build for that release branch.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20796 / 10.0.14393.7428 / 10.0.17763.6414 or later
Fixed in 10.0.10240.2079610.0.14393.742810.0.17763.6414
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update for CVE-2024-43572 immediately once released, as it addresses the RCE vulnerability in MMC. Prioritize workstations and servers where MMC is frequently used.

Recommended fix High confidence

Upgrade to the specific fixed build for your Windows version: 10.0.10240.20796 (Win10 1507), 10.0.14393.7428 (Win10 1607), 10.0.17763.6414 (Win10 1809), 10.0.19044.5011 (Win10 21h2), 10.0.19045.5011 (Win10 22h2), 10.0.22000.3260 (Win11 21h2), 10.0.22621.4317 (Win11 22h2), or 10.0.22631.4317 (Win11 2

  1. 1. Identify the current Windows version and build by opening Settings > System > About, or running 'winver' in the Run dialog
  2. 2. Determine which Windows 10 or 11 version and build is currently installed (1507, 1607, 1809, 21h2, 22h2, or 23h2)
  3. 3. For Windows 10 1507: Upgrade to Windows 10 build 10.0.10240.20796 or later via Windows Update or media update
  4. 4. For Windows 10 1607: Upgrade to Windows 10 build 10.0.14393.7428 or later via Windows Update or media update
  5. 5. For Windows 10 1809: Upgrade to Windows 10 build 10.0.17763.6414 or later via Windows Update or media update
  6. 6. For Windows 10 21h2: Upgrade to Windows 10 build 10.0.19044.5011 or later via Windows Update
  7. 7. For Windows 10 22h2: Upgrade to Windows 10 build 10.0.19045.5011 or later via Windows Update
  8. 8. For Windows 11 21h2: Upgrade to Windows 11 build 10.0.22000.3260 or later via Windows Update
Caveat Standard Windows update risks apply; ensure backups before applying updates; some older systems may require additional update prerequisites

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43572 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43572 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data