# CVE-2024-30051: Microsoft DWM Core Library Privilege Escalation

> An attacker can exploit a memory corruption flaw in the Windows DWM Core Library to escalate privileges on affected Windows systems.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 14 May 2024 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-rq9g-8pvx-hrqx

## What is CVE-2024-30051?

CVE-2024-30051 is a high-severity memory corruption vulnerability in Microsoft Windows 10 1507, published on 14 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Windows DWM Core Library Elevation of Privilege Vulnerability

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2024-30051?

It affects 11 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 21h2, Microsoft Windows 11 22h2, Microsoft Windows 11 23h2, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022.

## How do I fix CVE-2024-30051?

No fix has been published for CVE-2024-30051 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 4 Jun 2024.

## Is CVE-2024-30051 being exploited?

Yes. Attackers have exploited CVE-2024-30051 in the wild since at least 14 May 2024, including in ransomware campaigns.

Public exploit code:

- https://github.com/fortra/CVE-2024-30051 (github_poc): https://github.com/fortra/CVE-2024-30051
- Master's Thesis research on CVE-2024-30051 (Windows DWM Heap Overflow). Features a high-reliability exploit with automated heap spray optimization, real-time logging, and empirical success-rate analysis. Portfolio piece demonstrating advanced Windows binary exploitation, heap layout manipulation, and LPE via Desktop Window Manager. (github_poc): https://github.com/devianntsec/CVE-2024-30051

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-30051 and fix it if it is affected.

What it is: CVE-2024-30051 is a high-severity memory corruption vulnerability in Microsoft Windows 10 1507, published on 14 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-30051 in the wild since at least 14 May 2024, including in ransomware campaigns.

Affected product: Microsoft Windows 10 1507. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-30051/ (Markdown: https://insights.sbomify.com/CVE-2024-30051/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-30051
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-30051
- OSV: https://osv.dev/vulnerability/CVE-2024-30051

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-30051/
Summaries are generated and may contain mistakes; the official description above is the record.