Security Resilience

CVE-2023-36396

Microsoft Windows 11 22H2 ≤ 10.0.22621.2715

Published
14 November 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.017 76th percentile
Risk Priority 60 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-36396 is a high-severity Improper Resolution of Path Equivalence (CWE-41) vulnerability in Microsoft Windows 11 22H2. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked in the top 24% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Windows Compressed Folder Remote Code Execution Vulnerability

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
T1003.007 Proc Filesystem Credential Access
Adversaries may gather credentials from the proc filesystem or `/proc`.
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-26185Same product: Microsoft Windows 11 22H2
CVE-2024-38165Same product: Microsoft Windows 11 22H2
CVE-2025-21219Same product: Microsoft Windows 11 22H2
CVE-2024-30073Same product: Microsoft Windows 11 22H2
CVE-2025-21332Same product: Microsoft Windows 11 22H2
CVE-2025-54107Same product: Microsoft Windows 11 22H2
CVE-2025-21189Same product: Microsoft Windows 11 22H2
CVE-2025-21247Same product: Microsoft Windows 11 22H2
CVE-2025-21268Same product: Microsoft Windows 11 22H2
CVE-2025-21329Same product: Microsoft Windows 11 22H2

Affected Assets

microsoft
windows 11 22h2
≤ 10.0.22621.2715 · ≤ 10.0.22621.2715
microsoft
windows 11 23h2
≤ 10.0.22621.2715 · ≤ 10.0.22621.2715

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.

PR.IR-01 partial match
blocks

Path-equivalence flaws enable unauthorized file access that network segmentation and logical access controls can partially block.

PR.PS-06 partial match
blocks

Secure SDLC practices directly prevent introduction of improper path-resolution logic in software.

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.

blocks

Secure development lifecycle includes path-handling requirements that reduce equivalence-based disclosure.

blocks

Application security requirements can mandate canonicalization and input validation to block path equivalence.

blocks

A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust-external-input, security-oriented design reviews, hardening) that reach a minority slice of path-equivalence cases when applied to file-system or input-handling layers, but most CWE-41 instances arise from un-reviewed custom path canonicalization logic that the clause does not itself eliminate or block from exploitation.

prevents

Secure coding standards directly require canonical path resolution and input sanitization to prevent equivalence attacks.

finds

Security testing can detect path-equivalence flaws before release, partially fulfilling the control.

References