Evidence used
- CISA confirms exploitation in the wild.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 5.69% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2024
CVE-2024-30051High confidence
Microsoft DWM Core Library Privilege Escalation Vulnerability
Microsoft · DWM Core Library
7.8HighCVSS 3.1
Patch now
Patch availableCISA confirms exploitation in the wild and lists 2024-06-04 as the remediation due date.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 14 May 2024
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs Microsoft DWM Core Library and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
CISA confirms exploitation in the wild and lists 2024-06-04 as the remediation due date.
Patch available01
What, why and how
Microsoft DWM Core Library contains a privilege escalation vulnerability that allows an attacker to gain SYSTEM privileges.
What
Microsoft DWM Core Library contains a privilege escalation vulnerability that allows an attacker to gain SYSTEM privileges.
Why
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.
What
Microsoft DWM Core Library contains a privilege escalation vulnerability that allows an attacker to gain SYSTEM privileges.
Why
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation Confirmed in the wild
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2024-05-14. Known ransomware campaign use is recorded.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Heap-based Buffer Overflow → gain additional privileges
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-122 ↗
CWE-122: Heap-based Buffer Overflow. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- Windows Server 2022: 10.0.20348.0 < 10.0.20348.2461
- Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.3593
- Windows 10 Version 1809: 10.0.0 < 10.0.17763.5820, 10.0.17763.0 < 10.0.17763.5820
- Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.4412
- Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.3593
- Windows 11 version 21H2: 10.0.0 < 10.0.22000.2960
- Windows 11 version 22H2: 10.0.22621.0 < 10.0.22621.3593
- Windows Server 2016: 10.0.14393.0 < 10.0.14393.6981
- Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.5820
- Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.6981
- Windows 10 Version 1507: 10.0.10240.0 < 10.0.10240.20651
- Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.6981
- Windows Server 2019: 10.0.17763.0 < 10.0.17763.5820
- Windows 10 Version 21H2: 10.0.19043.0 < 10.0.19044.4412
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 14 May 2024 · Last source change 21 Oct 2025, 23:05 UTC · CWE-122 · Heap-based Buffer Overflow
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2024-27989
Product sourceCISA KEV
Remediation sourceCVE/CNA references
CWE sourceOther authority
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 10.0.17763.0 < 10.0.17763.5820; 10.0.0 < 10.0.17763.5820; 10.0.20348.0 < 10.0.20348.2461; 10.0.0 < 10.0.22000.2960; 10.0.19043.0 < 10.0.19044.4412; 10.0.22621.0 < 10.0.22621.3593 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.5820, 10.0.0 < 10.0.17763.5820; Windows Server 2019: 10.0.17763.0 < 10.0.17763.5820; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.5820; Windows Server 2022: 10.0.20348.0 < 10.0.20348.2461; Windows 11 version 21H2: 10.0.0 < 10.0.22000.2960; Windows 10 Version 21H2: 10.0.19043.0 < 10.0.19044.4412; Windows 11 version 22H2: 10.0.22621.0 < 10.0.22621.3593; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.4412; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.3593; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.3593; Windows 10 Version 1507: 10.0.10240.0 < 10.0.10240.20651; Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.6981; Windows Server 2016: 10.0.14393.0 < 10.0.14393.6981; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.6981 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
CVE published
Added to CISA KEV
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.