CVE-2024-38125
Microsoft Windows Server 2008 r2
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-38125 is a high-severity Numeric Truncation Error (CWE-197) vulnerability in Microsoft Windows Server 2008. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 7% 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.
CVE-2024-38125 is an elevation of privilege vulnerability in the Kernel Streaming WOW Thunk Service Driver. It carries a CVSS 3.1 score of 7.8 and is associated with CWE-197. The flaw affects a Windows kernel-mode component responsible for handling streaming operations in a WOW64 environment.
An attacker with local access and low privileges can exploit the issue without user interaction to obtain high impacts on confidentiality, integrity, and availability. The attack vector is local, with low complexity and unchanged scope, allowing the malicious actor to elevate privileges on the affected system.
Microsoft has published guidance for the vulnerability through its Security Response Center at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38125. The current EPSS score of 0.0943, with a recorded peak of 0.1029, indicates moderate but stable exploitation probability since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-37086
Vulnerability Data
Kernel Streaming WOW Thunk Service Driver Elevation of Privilege 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.