CVE-2024-30051
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 · uneditedWindows 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 confidenceA vulnerability in the Windows Desktop Window Manager (DWM) Core Library allows an authenticated attacker to elevate privileges, potentially executing arbitrary code in the context of a higher-privileged user.
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< 10.0.10240.20651< 10.0.14393.6981< 10.0.17763.5820< 10.0.19044.4412< 10.0.19045.4412< 10.0.22000.2960< 10.0.22621.3593< 10.0.22631.3593CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows 10 version build numberRun 'winver' from command prompt or check System Properties, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' and note the build number (e.g., 19045 for 22h2)Affected if The build number is less than the fixed version for your release: 10240.20651 for 1507, 14393.6981 for 1607, 17763.5820 for 1809, 19044.4412 for 21h2, or 19045.4412 for 22h2
-
Check Windows 11 version build numberRun 'winver' from command prompt or check System Properties, note the build number (e.g., 22621 for 22h2)Affected if The build number is less than the fixed version for your release: 22000.2960 for 21h2, 22621.3593 for 22h2, or 22631.3593 for 23h2
-
Confirm the exact OS build in registryRun 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v DisplayVersion' to get precise build informationAffected if The CurrentBuild value is lower than the threshold for your Windows release branch as listed in step 1 or 2
You are affected if your Windows version build number is below the threshold for your specific Windows release (10 or 11, and its sub-version like 21h2, 22h2, 23h2).
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.10240.2065110.0.14393.698110.0.17763.5820
Apply the Microsoft security update for CVE-2024-30051 via Windows Update or Microsoft Update Catalog, and validate successful installation.
- Open Windows Update by clicking the Start button and selecting Settings > Update & Security > Windows Update
- Click 'Check for updates' to scan for available updates
- Install any available security updates, specifically those released after May 2024 that address CVE-2024-30051
- If automatic updates are not enabled, manually download and install the appropriate security update from the Microsoft Update Catalog for your Windows version
- Restart the computer after installing the updates to complete the remediation
- Verify the installed updates by checking Windows Update history to confirm the security patch has been applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-30051 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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