Cyber Resilience

CVE-2023-24900

Memory Safety in Microsoft Windows Server 2008 r2

Memory Safety
Published
09 May 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.012 66th percentile
Risk Priority 50 floored blend · peak EPSS

Summary

CVE-2023-24900 is a medium-severity Out-of-bounds Read (CWE-125) vulnerability in Microsoft Windows Server 2008. Its CVSS base score is 5.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 34% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Windows NTLM Security Support Provider Information Disclosure Vulnerability

CWE(s)
CWE-125NVD-CWE-noinfo

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-21691Same product: Microsoft Windows 10 1507
CVE-2023-24931Same product: Microsoft Windows 10 1507
CVE-2023-21798Same product: Microsoft Windows 10 1507
CVE-2023-35296Same product: Microsoft Windows 10 1507
CVE-2023-35314Same product: Microsoft Windows 10 1507
CVE-2023-35319Same product: Microsoft Windows 10 1507
CVE-2023-32045Same product: Microsoft Windows 10 1507
CVE-2023-32017Same product: Microsoft Windows 10 1507
CVE-2023-35318Same product: Microsoft Windows 10 1507
CVE-2023-35299Same product: Microsoft Windows 10 1507

Affected Assets

microsoft
windows 10 1507
≤ 10.0.10240.19926
microsoft
windows 10 1607
≤ 10.0.14393.5921
microsoft
windows 10 1809
≤ 10.0.17763.4377
microsoft
windows 10 20h2
≤ 10.0.19042.2965
microsoft
windows 10 21h2
≤ 10.0.19044.2965
microsoft
windows 10 22h2
≤ 10.0.19045.2965
microsoft
windows 11 21h2
≤ 10.0.22000.1936
microsoft
windows 11 22h2
≤ 10.0.22000.1702
microsoft
windows server 2008
all versions, r2
microsoft
windows server 2012
all versions, r2
+3 more product configuration(s) — see NVD for full list

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.

PR.PS-06 mostly match
prevents

Secure-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.

PR.PS-02 partial match
prevents

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.

A.8.15 Logging partial match
finds

Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.

References