Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-30010 is a high-severity Relative Path Traversal (CWE-23) vulnerability in Microsoft Windows Server 2012. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 18% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — 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-30010 is a remote code execution vulnerability affecting the Windows Hyper-V component. It carries a CVSS 3.1 base score of 8.8 with an attack vector of network, low attack complexity, low privileges required, and no user interaction, resulting in high impact to confidentiality, integrity, and availability. The weakness is associated with CWE-23.
An authenticated attacker with low privileges can exploit the flaw over a network connection to execute arbitrary code on a vulnerable Hyper-V host. Successful exploitation grants the attacker full control equivalent to the compromised process privileges, enabling actions such as installing programs, viewing or modifying data, or creating new accounts.
Microsoft security advisories published at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-30010 detail the available patches and mitigation steps for affected Windows versions.
The associated EPSS score has remained flat at 0.1040 with no material rise observed since disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-27950
Vulnerability Data
Windows Hyper-V Remote Code Execution Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Explicit validation of path inputs stops .. sequences from ever being interpreted by the file system.
Access enforcement directly blocks unauthorized file reads/writes that result from unresolved .. sequences.
Information-flow rules can be configured to reject traversals that would move data outside an approved directory boundary.
Least privilege reduces the set of reachable files even when a traversal succeeds.
Secure-engineering principles require safe pathname construction and input neutralization before any file operation.
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 validation and path sanitization that prevent relative traversal.
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 catches path traversal via static/dynamic analysis, but does not itself implement the fix.
Secure development lifecycle mandates input validation and path-handling controls that directly prevent relative path traversal.
Application security requirements explicitly call for controls against path traversal and other injection flaws.
Secure architecture principles include directory isolation and canonicalization, reducing but not eliminating traversal risk.
Secure coding standards require neutralizing path traversal sequences, directly addressing CWE-23.
Information access restriction limits which files can be reached, mitigating impact but not preventing the traversal flaw.