dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-30032

HIGH · 7.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 10.0.10240.20651 / 10.0.14393.6981 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 DWM Core Library 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

Local privilege escalation vulnerability in the Windows Desktop Window Manager (DWM) Core Library that allows an authenticated attacker to gain elevated system privileges on the affected Windows machine.

MitigationApply Microsoft security updates for CVE-2024-30032 to all affected Windows systems as soon as feasible, following organization's patch management procedures.

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.20651
Windows 10 1607Operating system
Affected:< 10.0.14393.6981
Windows 10 1809Operating system
Affected:< 10.0.17763.5820
Windows 10 21h2Operating system
Affected:< 10.0.19044.4412
Windows 10 22h2Operating system
Affected:< 10.0.19045.4412
Windows 11 21h2Operating system
Affected:< 10.0.22000.2960
Windows 11 22h2Operating system
Affected:< 10.0.22621.3593
Windows 11 23h2Operating system
Affected:< 10.0.22631.3593

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 10 build number
    Open Command Prompt or PowerShell and run `winver` or `systeminfo | findstr /B /C:"OS Version"`. Locate the build number (e.g., 10.0.19045.xxxx)
    Affected if The build number is less than the threshold for your Windows 10 release: 1507 (<10.0.10240.20651), 1607 (<10.0.14393.6981), 1809 (<10.0.17763.5820), 21h2 (<10.0.19044.4412), or 22h2 (<10.0.19045.4412)
  2. Check Windows 11 build number
    Open Command Prompt or PowerShell and run `winver` or `systeminfo | findstr /B /C:"OS Version"`. Locate the build number (e.g., 10.0.22631.xxxx)
    Affected if The build number is less than the threshold for your Windows 11 release: 21h2 (<10.0.22000.2960), 22h2 (<10.0.22621.3593), or 23h2 (<10.0.22631.3593)
  3. Verify DWM process is running
    Open Task Manager, go to the Details tab, and look for "dwm.exe" under the Name column, or run `Get-Process -Name dwm` in PowerShell
    Affected if DWM is running (this is the default state on all affected Windows versions; the vulnerability applies when DWM is active)

Your system is affected if it runs any Windows 10 or Windows 11 version with a build number below the corresponding threshold listed above and DWM is enabled (standard on desktop Windows).

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.20651 / 10.0.14393.6981 / 10.0.17763.5820 or later
Fixed in 10.0.10240.2065110.0.14393.698110.0.17763.5820
Interim mitigation

Apply Microsoft security updates for CVE-2024-30032 to all affected Windows systems as soon as feasible, following organization's patch management procedures.

Recommended fix High confidence

Windows Security Update (CVE-2024-30032) - apply the appropriate monthly security update for your Windows version that includes the fix for build numbers listed above

  1. 1. Identify the current Windows version and build by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. 2. Determine which Windows version category applies (10 1507, 10 1607, 10 1809, 10 21h2, 10 22h2, 11 21h2, 11 22h2, or 11 23h2)
  3. 3. Apply the corresponding Windows Security Update that addresses CVE-2024-30032
  4. 4. For Windows 10 1507: install update with build 10.0.10240.20651 or later
  5. 5. For Windows 10 1607: install update with build 10.0.14393.6981 or later
  6. 6. For Windows 10 1809: install update with build 10.0.17763.5820 or later
  7. 7. For Windows 10 21h2: install update with build 10.0.19044.4412 or later
  8. 8. For Windows 10 22h2: install update with build 10.0.19045.4412 or later
Caveat Standard Windows update process; no expected breaking changes 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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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