Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-38080 is a high-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Microsoft Windows 11 21H2. 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 6% 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 SA-8 (Security and Privacy Engineering Principles) — 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-38080 is an elevation of privilege vulnerability in Windows Hyper-V, carrying a CVSS 3.1 base score of 7.8. The flaw is associated with CWE-190 and was publicly disclosed on 9 July 2024.
A local attacker who already possesses a low-privileged account on an affected Hyper-V host can exploit the issue without user interaction. Successful exploitation grants the attacker full control over the confidentiality, integrity, and availability of the system, effectively allowing a privilege escalation to SYSTEM-level access within the Hyper-V environment.
Microsoft has published guidance and patches through its Security Response Center, while CISA has added the CVE to its Known Exploited Vulnerabilities catalog, confirming active exploitation in the wild.
The EPSS score rose from a low baseline to a peak of 0.2197 before settling at the current value of 0.1420, indicating that exploitation interest increased after disclosure and that the vulnerability continues to warrant attention.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-37774
Vulnerability Data
Windows Hyper-V Elevation of Privilege Vulnerability
- CWE(s)
- KEV Date Added
- 09 July 2024
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds integer overflow defects before deployment.
Secure engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer overflow during calculation.
Input validation enforces bounds on values before arithmetic, stopping the conditions that trigger overflow or wraparound.
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 use of safe arithmetic, bounds checks, and testing that prevent integer overflows.
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 in development can detect integer overflows before release.
Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.
Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.