CVE-2023-21527
Memory Safety in Microsoft Windows 10 1809
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2023-21527 is a high-severity Wrap or Wraparound (CWE-191) vulnerability in Microsoft Windows 10 1809. 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 21% 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 iSCSI Service contains a denial-of-service vulnerability tracked as CVE-2023-21527. The flaw is present in the Windows iSCSI service and carries a CVSS 3.1 base score of 7.5, reflecting network attack vector, low attack complexity, and no required privileges or user interaction, with high impact on availability and no impact on confidentiality or integrity. The associated weakness identifiers are CWE-191 and NVD-CWE-noinfo.
An unauthenticated remote attacker can send specially crafted network traffic to an affected system and trigger the denial-of-service condition, rendering the iSCSI service unavailable. Because the attack requires no authentication or user interaction, it can be launched from anywhere on the network that can reach the target service.
Microsoft has published guidance for the issue at the Microsoft Security Response Center advisory page for CVE-2023-21527. The EPSS score for this CVE has remained flat at a peak of 0.2821 since disclosure, indicating no material increase in observed exploitation interest.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-25695
Vulnerability Data
Windows iSCSI Service 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 SDLC practices directly prevent integer underflow defects via input validation, bounds checking, and static analysis.
Vulnerability scanning and code analysis can surface underflow flaws after they are introduced.
Routine patching can remediate known underflow bugs once they are discovered in deployed software.
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 catches integer underflow defects before release.
Secure development lifecycle mandates input validation and arithmetic checks that prevent integer underflow.
Application security requirements include bounds checking and safe arithmetic to avoid underflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards directly prescribe safe integer handling and overflow/underflow prevention.