Cyber Resilience

CVE-2024-21442

Microsoft Windows 10 21H2 ≤ 10.0.19044.4170

Published
12 March 2024
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0083 54th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2024-21442 is a high-severity Improper Null Termination (CWE-170) vulnerability in Microsoft Windows 10 21H2. Its CVSS base score is 7.8 (High).

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

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Windows USB Print Driver Elevation of Privilege Vulnerability

CWE(s)
CWE-170NVD-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-38059Same product: Microsoft Windows 10 21H2
CVE-2024-20681Same product: Microsoft Windows 10 21H2
CVE-2024-26184Same product: Microsoft Windows 10 21H2
CVE-2024-43529Same product: Microsoft Windows 10 21H2
CVE-2024-38248Same product: Microsoft Windows 10 21H2
CVE-2024-38147Same product: Microsoft Windows 10 21H2
CVE-2024-38150Same product: Microsoft Windows 10 21H2
CVE-2024-38246Same product: Microsoft Windows 10 21H2
CVE-2024-43574Same product: Microsoft Windows 10 21H2
CVE-2023-36907Same product: Microsoft Windows 10 21H2

Affected Assets

microsoft
windows 10 21h2
≤ 10.0.19044.4170
microsoft
windows 10 22h2
≤ 10.0.19045.4170
microsoft
windows 11 21h2
≤ 10.0.22000.2836
microsoft
windows 11 22h2
≤ 10.0.22621.3296
microsoft
windows 11 23h2
≤ 10.0.22631.3296
microsoft
windows server 2022
≤ 10.0.20348.2340
microsoft
windows server 2022 23h2
≤ 10.0.25398.763

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing or incorrect string termination during code review or dynamic analysis.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can enforce safe string-handling practices that produce correct null termination.

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 enforce correct string/array termination via coding standards, reviews, and static analysis.

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 missing or incorrect null terminators before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and string handling rules that prevent missing null terminators.

A.8.26 Application security requirements partial match
prevents

Application security requirements can explicitly call for proper string termination and buffer handling.

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

Secure architecture principles include defensive coding practices that address buffer and string termination issues.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require correct null termination of strings and arrays.

References