Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2023-21813 is a high-severity Buffer Over-read (CWE-126) vulnerability in Microsoft Windows Server 2008. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked in the top 26% 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 Secure Channel, the component responsible for implementing TLS and other cryptographic protocols in Windows, is affected by CVE-2023-21813, a denial-of-service vulnerability. The flaw carries a CVSS 7.5 rating reflecting network attack vector, low complexity, and no required privileges or user interaction, with a high impact on availability and no impact on confidentiality or integrity; associated CWEs include CWE-126.
An unauthenticated remote attacker can send specially crafted network traffic to a vulnerable Windows system and trigger a crash or service disruption in the Secure Channel implementation, resulting in loss of availability for dependent services such as RDP, HTTPS, or any application relying on Schannel.
Microsoft Security Response Center advisories at the referenced URLs describe available security updates that address the issue and should be applied according to organizational patch-management processes.
The associated EPSS score has remained flat at 0.1372 with no material increase after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-25979
Vulnerability Data
Windows Secure Channel Denial of Service 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 directly prevent introduction of buffer over-read weaknesses.
Vulnerability identification processes can discover buffer over-read flaws via scanning or review.
Patching or replacing vulnerable software removes known instances of buffer over-read bugs.
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 can detect buffer over-reads before release.
Secure SDLC mandates input validation and bounds checking that can prevent buffer over-reads.
Application security requirements can specify buffer-size and bounds-checking rules.
Secure architecture principles include memory-safety and bounds-checking design choices.
Secure coding standards directly require bounds-checked buffer access, mitigating over-reads.