CVE-2024-21302

Windows Secure Kernel Mode Elevation of Privilege Vulnerability

MEDIUM

6.7

CVSS Score

Published: August 8, 2024 at 01:59 AM UTC

Updated: June 17, 2026 at 07:08 AM UTC

14 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows 10 1809

Using Windows 10 Version 1809 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1809 - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM6.7

Exploit prediction

EPSS 2%

SSVC

No known exploit

Description

Summary: As of July 8, 2025 Microsoft has completed mitigations to address this vulnerability. See KB5042562: Guidance for blocking rollback of virtualization-based security related updates and the Recommended Actions section of this CVE for guidance on how to protect your systems from this vulnerability. An elevation of privilege vulnerability exists in Windows based systems supporting Virtualization Based Security (VBS), including a subset of Azure Virtual Machine SKUS. This vulnerability enables an attacker with administrator privileges to replace current versions of Windows system files with outdated versions. By exploiting this vulnerability, an attacker could reintroduce previously mitigated vulnerabilities, circumvent some features of VBS, and exfiltrate data protected by VBS. Update: July 10, 2025 Microsoft has addressed this vulnerability for Windows 10 1507, Windows 10, version 1607, Windows 10, version 1809, and Windows Server 2016 and Windows Server 2018. This ensures that mitigations are available to protect all supported versions of Windows 10 and Windows 11 from this vulnerability. See the available mitigations and deployment guidelines described in KB5042562: Guidance for blocking rollback of virtualization-based security related updates. Update: August 13, 2024 Microsoft has released the August 2024 security updates that include an opt-in revocation policy mitigation to address this vulnerability. Customers running affected versions of Windows are encouraged to review KB5042562: Guidance for blocking rollback of virtualization-based security related updates to assess if this opt-in policy meets the needs of their environment before implementing this mitigation. There are risks associated with this mitigation that should be understood prior to applying it to your systems. Detailed information about these risks is also available in KB5042562. Details: A security researcher informed Microsoft of an elevation of privilege vulnerability in Windows 10, Windows 11, Windows Server 2016, and higher based systems including Azure Virtual Machines (VM) that support VBS. For more information on Windows versions and VM SKUs supporting VBS, reference: Virtualization-based Security (VBS) | Microsoft Learn. The vulnerability enables an attacker with administrator privileges on the target system to replace current Windows system files with outdated versions. Successful... See more at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21302

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Windows 10 1507 · Microsoft

95%

v < 10.0.10240.2071010.0.10240.0 ≤ v < 10.0.10240.2107310.0.10240.0

Affected range stops below 10.0.10240.20710, so it looks safe — our inference, not a vendor statement

Affected range stops below 10.0.10240.21073, so it looks safe — our inference, not a vendor statement

Windows 10 1607 · Microsoft

95%

v < 10.0.14393.725910.0.14393.0 ≤ v < 10.0.14393.824610.0.14393.0

Affected range stops below 10.0.14393.7259, so it looks safe — our inference, not a vendor statement

Affected range stops below 10.0.14393.8246, so it looks safe — our inference, not a vendor statement

Windows 10 1809 · Microsoft

95%

v < 10.0.17763.618910.0.17763.0 ≤ v < 10.0.17763.755810.0.17763.0

Affected range stops below 10.0.17763.6189, so it looks safe — our inference, not a vendor statement

Affected range stops below 10.0.17763.7558, so it looks safe — our inference, not a vendor statement

Windows 10 21H2 · Microsoft

95%

v < 10.0.19044.478010.0.19044.0 ≤ v < 10.0.19044.478010.0.19044.0

Affected range stops below 10.0.19044.4780, so it looks safe — our inference, not a vendor statement

Windows 10 22H2 · Microsoft

95%

v < 10.0.19045.478010.0.19045.0 ≤ v < 10.0.19045.573710.0.19045.0

Affected range stops below 10.0.19045.4780, so it looks safe — our inference, not a vendor statement

Affected range stops below 10.0.19045.5737, so it looks safe — our inference, not a vendor statement

Windows 11 21H2 · Microsoft

95%

v < 10.0.22000.314710.0.22000.0 ≤ v < 10.0.19044.573710.0.22000.0

Affected range stops below 10.0.19044.5737, so it looks safe — our inference, not a vendor statement

Affected range stops below 10.0.22000.3147, so it looks safe — our inference, not a vendor statement

Windows 11 22H2 · Microsoft

95%

v < 10.0.22621.403710.0.22621.0 ≤ v < 10.0.22621.518910.0.22621.0

Affected range stops below 10.0.22621.4037, so it looks safe — our inference, not a vendor statement

Affected range stops below 10.0.22621.5189, so it looks safe — our inference, not a vendor statement

Windows 11 23H2 · Microsoft

95%

v < 10.0.22631.403710.0.22631.0 ≤ v < 10.0.22631.518910.0.22631.0

Affected range stops below 10.0.22631.4037, so it looks safe — our inference, not a vendor statement

Affected range stops below 10.0.22631.5189, so it looks safe — our inference, not a vendor statement

Windows 11 24H2 · Microsoft

95%

v < 10.0.26100.145710.0.26100.0 ≤ v < 10.0.26100.377510.0.26100.0

Affected range stops below 10.0.26100.1457, so it looks safe — our inference, not a vendor statement

Affected range stops below 10.0.26100.3775, so it looks safe — our inference, not a vendor statement

Windows Server 2016 · Microsoft

95%

v < 10.0.14393.725910.0.14393.0 ≤ v < 10.0.14393.824610.0.14393.0

Affected range stops below 10.0.14393.7259, so it looks safe — our inference, not a vendor statement

Affected range stops below 10.0.14393.8246, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21302

References (1)

Vendor AdvisoryPatch

Source: [email protected]

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21302

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.7MEDIUMmicrosoft

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-284NVD-CWE-Other

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card