Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-32054 is a high-severity Absolute Path Traversal (CWE-36) vulnerability in Microsoft Windows Server 2012. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 41% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-36341
Vulnerability Data
Volume Shadow Copy Elevation of Privilege Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
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 absolute path 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.
A.8.25 mandates secure SDLC practices (secure requirements, checkpoints, secure coding guidelines, testing including code scans/penetration tests) that reach many path-traversal instances in custom software, but leaves a bounded remainder (e.g. third-party components, misconfigured outsourced development, or incomplete enforcement of guidelines) where the weakness can still be introduced and exploited.
Application security requirements typically mandate controls against path traversal in file-access functions.
A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust-external-input, hardening, design review against attack patterns) that reach a minority slice of absolute path traversal (e.g. explicit path canonicalization rules or sandboxing), but most instances arise from ordinary string-concatenation flaws in custom code that the clause's high-level engineering principles do not themselves stop from being written or exploited.
Secure coding standards directly require neutralization of absolute path sequences in pathname construction.
Security testing in development can detect absolute path traversal via static analysis and fuzzing.