CVE-2024-43572

Microsoft Management Console Remote Code Execution Vulnerability

HIGH
7.8
CVSS Score
Published: October 8, 2024 at 05:36 PM UTC
Updated: June 17, 2026 at 07:51 AM UTC
16 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 10 Version 1809 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1809 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploitation
CISA KEV
Exploit prediction
EPSS 67%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score66.7%

EPSS (Exploit Prediction Scoring System) estimates a 66.7% chance this CVE is exploited in the wild within the next 30 days — higher than 99% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

Microsoft Windows Management Console contains unspecified vulnerability that allows for remote code execution.

Required Action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Ransomware Use
Unknown
Added to KEV
Oct 8, 2024
Remediation Due
Oct 29, 2024
726 days overdue

Description

Microsoft Management Console Remote Code Execution Vulnerability

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.10240.2079610.0.10240.0 ≤ v < 10.0.10240.2079610.0.10240.0
Affected range stops below 10.0.10240.20796, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.742810.0.14393.0 ≤ v < 10.0.14393.742810.0.14393.0
Affected range stops below 10.0.14393.7428, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.641410.0.17763.0 ≤ v < 10.0.17763.641410.0.17763.0
Affected range stops below 10.0.17763.6414, so it looks safe — our inference, not a vendor statement
v < 10.0.19044.501110.0.19043.0 ≤ v < 10.0.19044.501110.0.19043.0
Affected range stops below 10.0.19044.5011, so it looks safe — our inference, not a vendor statement
v < 10.0.19045.501110.0.19045.0 ≤ v < 10.0.19045.501110.0.19045.0
Affected range stops below 10.0.19045.5011, so it looks safe — our inference, not a vendor statement
v < 10.0.22000.326010.0.22000.0 ≤ v < 10.0.22000.326010.0.22000.0
Affected range stops below 10.0.22000.3260, so it looks safe — our inference, not a vendor statement
v < 10.0.22621.431710.0.22621.0 ≤ v < 10.0.22621.431710.0.22621.0
Affected range stops below 10.0.22621.4317, so it looks safe — our inference, not a vendor statement
v < 10.0.22631.431710.0.22631.0 ≤ v < 10.0.22631.431710.0.22631.0
Affected range stops below 10.0.22631.4317, so it looks safe — our inference, not a vendor statement
v < 10.0.26100.203310.0.26100.0 ≤ v < 10.0.26100.203310.0.26100.0
Affected range stops below 10.0.26100.2033, so it looks safe — our inference, not a vendor statement
6.0.6003.0 ≤ v < 6.0.6003.229186.1.7601.0 ≤ v < 6.1.7601.273666.0.6003.06.1.7601.0r2 sp1sp2
Affected range stops below 6.0.6003.22918, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.7601.27366, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCActiveNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-707NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card