Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-36424 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Microsoft Windows 10 1809. 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 4% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
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-2023-36424 is an elevation-of-privilege vulnerability in the Windows Common Log File System (CLFS) Driver, stemming from an out-of-bounds read (CWE-125). The flaw affects the kernel-mode driver responsible for handling log files on Windows systems and carries a CVSS 3.1 score of 7.8, reflecting local attack vector, low complexity, and low required privileges.
A local attacker with a low-privileged account can exploit the flaw to read memory beyond intended bounds, enabling escalation to higher privileges and full compromise of confidentiality, integrity, and availability on the affected host.
Microsoft has published updates addressing the issue through its Security Response Center, while CISA includes the CVE in its Known Exploited Vulnerabilities catalog, indicating that federal agencies must apply the patches according to the published timelines.
EPSS for the vulnerability rose from a low baseline to a peak of 0.2029 on 2025-12-11 before receding to the current value of 0.0976, demonstrating a clear post-disclosure increase in exploitation interest that later moderated.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-40389
Vulnerability Data
Windows Common Log File System Driver Elevation of Privilege Vulnerability
- CWE(s)
- KEV Date Added
- 13 April 2026
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-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.
Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.
Routine patching replaces vulnerable code containing out-of-bounds read flaws.
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 and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.
Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.
Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.
Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.
Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.
Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.