dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-21436

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 Installer 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

CVE-2024-21436 is an elevation of privilege vulnerability in the Windows Installer component that allows an authenticated attacker to gain higher privileges on the affected system. The vulnerability likely involves improper validation or handling during Windows Installer operations.

MitigationApply the Microsoft security update for CVE-2024-21436 via Windows Update or deploy the corresponding KB patch to all affected Windows systems.

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 Windows version and build number
    Open Command Prompt or PowerShell and run: winver or systeminfo | findstr /B /C:"OS Name" /C:"OS Version". Alternatively, run 'ver' command or check System Properties.
    Affected if The displayed build number is lower than the thresholds in the affected versions list for your Windows release.
  2. Identify exact Windows 10 release
    Run 'winver' to see the specific Windows 10 release name (such as 1507, 1607, 1809, 21h2, or 22h2). The Windows 10 version can also be found in Settings > System > About.
    Affected if You are running Windows 10 1507, 1607, 1809, 21h2, or 22h2 with a build number below the corresponding threshold.
  3. Identify exact Windows 11 release
    Run 'winver' or check Settings > System > About to determine if you are on Windows 11 21h2, 22h2, or 23h2.
    Affected if You are running Windows 11 21h2, 22h2, or 23h2 with a build number below the corresponding threshold.
  4. Compare build number against CVE thresholds
    Note your exact build number (for example, 10.0.19045.1234) and compare the fourth segment (the revision number) to the threshold values: Windows 10 22h2 threshold is 10.0.19045.4170, Windows 11 22h2 threshold is 10.0.22621.3296, etc.
    Affected if Your build number is less than the specified threshold for your Windows version and release.

You are affected if your Windows version and build number fall within any of the affected ranges listed and you have an authenticated user context that could trigger the Windows Installer vulnerability.

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 Microsoft security update for CVE-2024-21436 via Windows Update or deploy the corresponding KB patch to all affected Windows systems.

Recommended fix High confidence

Upgrade to Windows build >= 10.0.10240.20526 (1507), >= 10.0.14393.6796 (1607), >= 10.0.17763.5576 (1809), >= 10.0.19044.4170 (21h2), >= 10.0.19045.4170 (22h2), >= 10.0.22000.2836 (Win11 21h2), >= 10.0.22621.3296 (Win11 22h2), or >= 10.0.22631.3296 (Win11 23h2)

  1. 1. Check current Windows version by running 'winver' or 'systeminfo' from command prompt
  2. 2. Open Windows Settings and navigate to 'Update & Security' > 'Windows Update'
  3. 3. Click 'Check for updates' to download and install the latest security updates
  4. 4. Alternatively, manually download the specific KB patch from Microsoft's Update Catalog (search for the KB number associated with CVE-2024-21436 for your Windows version)
  5. 5. Restart the computer after the update is installed
  6. 6. Verify the update was successful by checking that the Windows build number matches or exceeds the fixed version for your release (e.g., 10.0.19045.4170 or higher for Windows 10 22h2)
Caveat Standard Windows security updates rarely introduce breaking changes, but verify compatibility with line-of-business applications after updating

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21436 — 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-21436 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