CVE-2024-30051: Microsoft DWM Core Library Privilege Escalation
Microsoft DWM Core Library · listed in the CISA catalog of actively exploited vulnerabilities since 2024-05-14.
- CVSS v3.1 (CVE record)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 6.2%
- higher than 93.6% of all CVEs
- Added to CISA KEV
- 2024-05-14
- US federal due date 2024-06-04
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2024-30051 explained
CVE-2024-30051 is a privilege escalation vulnerability in the Microsoft DWM Core Library on Windows, classified as a heap-based buffer overflow. A local attacker with low privileges can gain SYSTEM privileges. CISA lists it as known exploited, including known use in ransomware campaigns, which makes prompt patching important.
Impact
An attacker who can already run code on a system with low privileges can escalate to SYSTEM without user interaction. This gives high impact to confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected system. CISA does not consider it automatable, so exploitation needs local access per target. Attackers are known to exploit it, and CISA reports known ransomware use.
Who is affected
Affected are Windows 10 Version 1507 (fixed in 10.0.10240.20651), 1607 (10.0.14393.6981), 1809 and Windows Server 2019 including Server Core (10.0.17763.5820), Windows 10 21H2 (10.0.19044.4412), 22H2 (10.0.19045.4412), Windows Server 2022 (10.0.20348.2461), Windows 11 21H2 (10.0.22000.2960), 22H2 (10.0.22621.3593), and 22H3 and 23H2 (10.0.22631.3593). Earlier builds of each are affected. The page lists two further products.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft DWM Core Library contains a privilege escalation vulnerability that allows an attacker to gain SYSTEM privileges.
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows 10 Version 180932-bit, x64, ARM64AffectedFixed in
- < 10.0.17763.5820
- 10.0.17763.5820
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.5820
- 10.0.17763.5820
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.5820
- 10.0.17763.5820
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.2461
- 10.0.20348.2461
- Microsoft Windows 11 version 21H2x64, ARM64AffectedFixed in
- < 10.0.22000.2960
- 10.0.22000.2960
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.4412
- 10.0.19044.4412
- Microsoft Windows 11 version 22H2ARM64, x64AffectedFixed in
- < 10.0.22621.3593
- 10.0.22621.3593
- Microsoft Windows 10 Version 22H2x64, ARM64, 32-bitAffectedFixed in
- < 10.0.19045.4412
- 10.0.19045.4412
- Microsoft Windows 11 version 22H3ARM64AffectedFixed in
- < 10.0.22631.3593
- 10.0.22631.3593
- Microsoft Windows 11 Version 23H2x64AffectedFixed in
- < 10.0.22631.3593
- 10.0.22631.3593
- Microsoft Windows 10 Version 150732-bit, x64AffectedFixed in
- < 10.0.10240.20651
- 10.0.10240.20651
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.6981
- 10.0.14393.6981
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.6981
- 10.0.14393.6981
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.6981
- 10.0.14393.6981
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 180932-bit, x64, ARM64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
| Microsoft Windows 11 version 21H2x64, ARM64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H2ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H2x64, ARM64, 32-bit |
|
|
| Microsoft Windows 11 version 22H3ARM64 |
|
|
| Microsoft Windows 11 Version 23H2x64 |
|
|
| Microsoft Windows 10 Version 150732-bit, x64 |
|
|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1809: 10.0.17763.5820
- Microsoft Windows Server 2019: 10.0.17763.5820
- Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.5820
- Microsoft Windows Server 2022: 10.0.20348.2461
- Microsoft Windows 11 version 21H2: 10.0.22000.2960
- Microsoft Windows 10 Version 21H2: 10.0.19044.4412
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2024-30051
- CISA's deadline for US federal agencies: 2024-06-04 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the Microsoft security update that brings each system to the fixed build listed for its Windows version.
- Prioritize patching, since CISA lists this vulnerability as known exploited and used in ransomware.
- Verify build numbers across all Windows 10, Windows 11 and Windows Server 2019/2022 systems after updating.
- Limit local logon and low-privileged code execution on critical systems until patches are applied.
- Check systems for signs of compromise, such as unexpected SYSTEM-level activity or ransomware indicators.
- Follow the Microsoft advisory; per CISA, discontinue use if mitigations are unavailable.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-122 Heap-based Buffer Overflow
Questions about CVE-2024-30051
- Can this be exploited remotely?
- No. The attack vector is local and requires low privileges. An attacker must already be able to run code on the system, then uses the flaw to gain SYSTEM privileges.
- Is this vulnerability being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-05-14 and reports known ransomware use. US federal agencies had a due date of 2024-06-04.
- Which build fixes Windows 11 23H2?
- Windows 11 Version 23H2 is fixed in build
10.0.22631.3593. Earlier builds are affected.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.