Cyber Resilience

CVE-2023-24944

Memory Safety in Microsoft Windows 10 1809 ≤ 10.0.17763.4377

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

Summary

CVE-2023-24944 is a medium-severity Type Confusion (CWE-843) vulnerability in Microsoft Windows 10 1809. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 49th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Windows Bluetooth Driver Information Disclosure Vulnerability

CWE(s)
CWE-843NVD-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 →
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-2024-30034Same product: Microsoft Windows 10 1809
CVE-2023-35356Same product: Microsoft Windows 10 1809
CVE-2023-24929Same product: Microsoft Windows 10 1809
CVE-2023-24927Same product: Microsoft Windows 10 1809
CVE-2023-24885Same product: Microsoft Windows 10 1809
CVE-2023-28243Same product: Microsoft Windows 10 1809
CVE-2023-35297Same product: Microsoft Windows 10 1809
CVE-2023-36578Same product: Microsoft Windows 10 1809
CVE-2023-21675Same product: Microsoft Windows 10 1809
CVE-2024-38178Same product: Microsoft Windows 10 1809

Affected Assets

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 2019
all versions
microsoft
windows server 2022
all versions

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.2
  • V3.2.3
  • V15.3.5

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 SDLC practices directly prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional weaknesses.

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 can detect type-confusion vulnerabilities through fuzzing and static analysis.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates type-safe design and review that can catch type-confusion flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify strong typing and interface contracts that reduce type confusion.

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

Secure architecture principles promote type-safe languages and memory-safety mechanisms that mitigate type confusion.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.

References