dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2024-30035

HIGH · 7.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 10.0.17763.5820 / 10.0.19044.4412 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 · low confidence

This is an Elevation of Privilege vulnerability in the Windows Desktop Window Manager (DWM) Core Library. The DWM is responsible for compositing visual elements on the Windows desktop. The vulnerability allows a local authenticated attacker to gain elevated privileges on the affected system.

MitigationApply the Microsoft security update for CVE-2024-30035, typically delivered through Windows Update or enterprise patch management 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 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
Windows Server 2019Operating system
Affected:< 10.0.17763.5820
Windows Server 2022Operating system
Affected:< 10.0.20348.2461

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 build number
    Run 'winver' or 'systeminfo | findstr /C:"Build"' from Command Prompt to retrieve the OS build number
    Affected if The build number is lower than the threshold for your Windows version (10 1809: <17763.5820, 10 21h2: <19044.4412, 10 22h2: <19045.4412, 11 21h2: <22000.2960, 11 22h2: <22621.3593, 11 23h2: <22631.3592, Server 2019: <17763.5820, Server 2022: <20348.2461)
  2. Identify Windows release version
    Run 'winver' to confirm whether the system is Windows 10 (1809, 21h2, or 22h2), Windows 11 (21h2, 22h2, or 23h2), or Windows Server (2019 or 2022)
    Affected if The identified release falls within the affected product list and the build number is below the corresponding threshold
  3. Verify DWM service status
    The DWM service (Desktop Window Manager) runs by default on desktop Windows editions; on Server editions, confirm whether the 'Desktop Experience' or DWM feature is installed. Check via 'Get-Service DWM' in PowerShell
    Affected if DWM is actively running or the Desktop Experience feature is enabled on affected Windows versions with vulnerable build numbers

The system is affected if it runs any of the listed Windows versions with a build number lower than the specified threshold and has DWM functionality present.

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.17763.5820 / 10.0.19044.4412 / 10.0.19045.4412 or later
Fixed in 10.0.17763.582010.0.19044.441210.0.19045.4412
Interim mitigation

Apply the Microsoft security update for CVE-2024-30035, typically delivered through Windows Update or enterprise patch management systems.

Recommended fix High confidence

Apply the May 2024 Windows Security Update (CVE-2024-30035) to reach the version numbers specified: Windows 10 1809/Windows Server 2019 to 10.0.17763.5820, Windows 10 21H2 to 10.0.19044.4412, Windows 10 22H2 to 10.0.19045.4412, Windows 11 21H2 to 10.0.22000.2960, Windows 11 22H2 to 10.0.22621.3593,

  1. 1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows 10 or 11 version or Windows Server version is currently installed
  3. 3. Apply the appropriate Windows Security Update (KB) that addresses CVE-2024-30035
  4. 4. For Windows 10 1809 and Windows Server 2019: Install update reaching version 10.0.17763.5820 or later
  5. 5. For Windows 10 21H2: Install update reaching version 10.0.19044.4412 or later
  6. 6. For Windows 10 22H2: Install update reaching version 10.0.19045.4412 or later
  7. 7. For Windows 11 21H2: Install update reaching version 10.0.22000.2960 or later
  8. 8. For Windows 11 22H2: Install update reaching version 10.0.22621.3593 or later
Caveat Standard Windows update with no expected breaking changes; as with any security update, test in a staging environment if possible

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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