CVE-2023-21682
Memory Safety in Microsoft Windows 10 1809
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2023-21682 is a medium-severity Out-of-bounds Read (CWE-125) vulnerability in Microsoft Windows 10 1809. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 30% 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.
Windows Point-to-Point Protocol (PPP) contains an information disclosure vulnerability tracked as CVE-2023-21682 and assigned CWE-125. The flaw affects the PPP implementation in Windows and carries a CVSS 3.1 base score of 5.3 reflecting a network-reachable read of limited sensitive data without authentication or user interaction.
An unauthenticated remote attacker can send crafted network traffic to a vulnerable Windows system running PPP and obtain partial memory contents. The attack requires no privileges or user action and results only in confidentiality impact, with no integrity or availability consequences.
Microsoft has published remediation guidance and patches through its Security Response Center at the referenced advisory URL. The EPSS score has remained flat at 0.0914 with no material increase since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-25849
Vulnerability Data
Windows Point-to-Point Protocol (PPP) Information Disclosure 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.