CVE-2023-21539
Memory Safety in Microsoft Windows 10 20H2
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-21539 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Microsoft Windows 10 20H2. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 36% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV 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-21539 is a remote code execution vulnerability affecting the Windows Authentication component. It carries a CVSS 3.1 base score of 7.5 and is associated with CWE-125. The flaw permits an attacker to execute arbitrary code on an affected system when specific conditions are met during authentication processing.
An authenticated user with low privileges can exploit the issue over a network connection, though successful exploitation requires high attack complexity and no user interaction. Successful attacks can result in full compromise of confidentiality, integrity, and availability on the target system.
Microsoft security advisories for CVE-2023-21539, available at the referenced MSRC update guide, detail the affected Windows versions and the corresponding security updates that address the vulnerability.
The EPSS score for this CVE rose from lower values to a peak of 0.0976 on 2025-01-22 before receding to the current 0.0305, indicating a period of increased exploitation interest after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-25706
Vulnerability Data
Windows Authentication Remote Code Execution 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-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.