dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-21437

HIGH · 7.8 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to 10.0.10240.20526 / 10.0.14393.6796 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Windows Graphics Component Elevation of Privilege Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an Elevation of Privilege vulnerability in the Windows Graphics Component. Attackers could potentially exploit this to gain higher system privileges by targeting graphics subsystem components.

MitigationApply the relevant Microsoft security update for this vulnerability through Windows Update or your patch management system.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20526
Windows 10 1607Operating system
Affected:< 10.0.14393.6796
Windows 10 1809Operating system
Affected:< 10.0.17763.5576
Windows 10 21h2Operating system
Affected:< 10.0.19044.4170
Windows 10 22h2Operating system
Affected:< 10.0.19045.4170
Windows 11 21h2Operating system
Affected:< 10.0.22000.2836
Windows 11 22h2Operating system
Affected:< 10.0.22621.3296
Windows 11 23h2Operating system
Affected:< 10.0.22631.3296

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Windows version
    Open Command Prompt and run 'winver' to display the Windows version and build number, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' for detailed information
    Affected if The displayed build number is lower than the fixed version for your specific Windows release (see version ranges in the CVE description)
  2. Identify exact Windows release
    Note whether your system is Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 21h2, 22h2, or 23h2 - this determines which version threshold applies
    Affected if You are running any of these releases at a build number below its respective fixed threshold
  3. Confirm graphics subsystem is present
    Verify the Windows Graphics Component is available by checking that display drivers or graphics-related services are present - this is typically default on Windows desktops and servers with GUI
    Affected if The graphics subsystem is present (which is the default configuration on affected Windows versions)
  4. Alternative version check via registry
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and '/v DisplayVersion' (if available) to retrieve the exact build number programmatically
    Affected if The retrieved build number falls below the threshold for your Windows release as listed in the affected versions

You are affected if your Windows version (10 or 11) build number is lower than the fixed threshold for your specific release branch, and the graphics subsystem is enabled (default state).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20526 / 10.0.14393.6796 / 10.0.17763.5576 or later
Fixed in 10.0.10240.2052610.0.14393.679610.0.17763.5576
Interim mitigation

Apply the relevant Microsoft security update for this vulnerability through Windows Update or your patch management system.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20526+ | Windows 10 1607: 10.0.14393.6796+ | Windows 10 1809: 10.0.17763.5576+ | Windows 10 21h2: 10.0.19044.4170+ | Windows 10 22h2: 10.0.19045.4170+ | Windows 11 21h2: 10.0.22000.2836+ | Windows 11 22h2: 10.0.22621.3296+ | Windows 11 23h2: 10.0.22631.3296+

  1. Press Win+R, type 'winver', and press Enter to check your current Windows version
  2. Note the full version number (e.g., 10.0.19045.4170)
  3. Press Win+I to open Settings, then go to Windows Update
  4. Click 'Check for updates' and install all available updates
  5. Alternatively, manually download and install the appropriate Cumulative Security Update from the Microsoft Update Catalog for your Windows version
  6. After installation, restart your computer to apply the security patch
  7. Verify the fix by checking that your version meets or exceeds the minimum fixed version for your Windows release
Caveat Standard Windows update; no breaking changes expected for this security patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21437 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21437 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data