Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-21692 is a critical-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Microsoft Windows 10 1809. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 3% 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.
Microsoft Protected Extensible Authentication Protocol (PEAP) contains a remote code execution vulnerability tracked as CVE-2023-21692. The flaw affects the PEAP implementation in Microsoft Windows and carries a CVSS 3.1 score of 9.8, reflecting network-accessible attack conditions with no required privileges or user interaction and full impact on confidentiality, integrity, and availability. Associated weakness identifiers include CWE-122.
An unauthenticated attacker able to reach a vulnerable PEAP endpoint over the network can trigger the flaw to execute arbitrary code with the privileges of the affected process. Successful exploitation therefore grants complete control over the target system without any prior authentication or user assistance.
Microsoft security advisories hosted at the MSRC update guide for CVE-2023-21692 describe available patches and recommend applying the updates released for supported Windows versions to eliminate the vulnerability.
EPSS probability for the CVE rose from lower values after disclosure to a recorded peak of 0.3048 on 2025-12-11 before receding to the current level of 0.1667, indicating a later surge in observed exploitation interest.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-25859
Vulnerability Data
Microsoft Protected Extensible Authentication Protocol (PEAP) Remote Code Execution Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.4.1
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 directly require bounds checking and safe memory handling that prevent heap overflows.
Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.
Timely patching removes known heap-overflow instances after they exist.
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 can detect heap overflows before release.
Secure development lifecycle mandates practices that reduce the likelihood of introducing heap overflows.
Application security requirements can specify bounds-checking and safe memory APIs that mitigate heap overflows.
Secure architecture and engineering principles include memory-safety and input-validation controls that address heap overflows.
Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.
Change management ensures controlled deployment of fixes for discovered heap-overflow vulnerabilities.