CVE-2024-43639
Microsoft Windows Server 2012 r2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-43639 is a critical-severity Numeric Truncation Error (CWE-197) vulnerability in Microsoft Windows Server 2012. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — 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.
The vulnerability CVE-2024-43639 is a remote code execution flaw in the Windows KDC Proxy component, carrying a CVSS 3.1 base score of 9.8 under the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H and mapped to CWE-197.
An unauthenticated attacker with network access can exploit the issue without user interaction to achieve arbitrary code execution, resulting in full compromise of confidentiality, integrity, and availability on affected Windows systems.
Microsoft published an advisory for the vulnerability at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43639. The associated EPSS score rose from a low baseline to a peak of 0.1276 on 2025-12-11 before receding to the current value of 0.0285, indicating that exploitation interest emerged after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-40384
Vulnerability Data
Windows KDC Proxy Remote Code Execution Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover truncation errors through static analysis, dynamic testing, or code review.
Documented development standards and tools can mandate use of safe arithmetic libraries or explicit checks against truncation.
Engineering principles can require safe type conversions and avoidance of narrowing casts that cause truncation.
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 prevent truncation errors via reviews, static analysis, and safe type 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.
Security testing can detect truncation bugs through static analysis and fuzzing.
Secure development lifecycle mandates practices that can catch numeric truncation during design and code review.
Application security requirements can specify safe numeric handling and data-type constraints.
Secure architecture principles include choosing appropriate data types and avoiding unsafe casts.
Secure coding standards directly prohibit unsafe narrowing conversions and truncation.