CVE-2024-43572
Microsoft Windows 10 21H2 ≤ 10.0.19044.5011
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2024-43572 is a high-severity Improper Neutralization (CWE-707) vulnerability in Microsoft Windows 10 21H2. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.8% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-43572 is a remote code execution vulnerability in the Microsoft Management Console. The flaw carries a CVSS 7.8 rating reflecting local attack vector, low complexity, no required privileges, and required user interaction, with high impact on confidentiality, integrity, and availability. It affects the MMC component on supported Windows systems.
An attacker who can convince a user to open a malicious file or link can execute arbitrary code in the context of the logged-on user, potentially installing programs, viewing or modifying data, or creating new accounts with full user rights.
Microsoft has published an advisory detailing the affected builds and available updates, while CISA has added the CVE to its Known Exploited Vulnerabilities catalog, confirming active exploitation in the wild and directing organizations to apply the vendor patches.
The EPSS score reached a peak of 0.5404 before receding to its current value of 0.4894.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-40326
Vulnerability Data
Microsoft Management Console Remote Code Execution Vulnerability
- CWE(s)
- KEV Date Added
- 08 October 2024
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 4 OS baselines
V1.3.9
Mitigating Controls (NIST 800-53 r5) AI
Developer testing can discover missing or incorrect neutralization logic.
Input validation directly enforces well-formed data and security properties before processing.
Output filtering enforces neutralization properties on data leaving the system.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input/output neutralization and validation to prevent malformed data handling.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards directly require proper neutralization of inputs and outputs, eliminating CWE-707.
Security testing can detect neutralization flaws but does not itself implement the required controls.
Secure development life cycle mandates input validation and output encoding that directly prevent improper neutralization.
Application security requirements explicitly call for data validation and sanitization controls addressing neutralization weaknesses.
Secure architecture principles include canonicalization and safe parsing, mitigating but not fully covering neutralization issues.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 9 (1 rule)
- V-271523 OL 9 must check the GPG signature of locally installed software packages before installation. prevents CWE-707