Cyber Resilience

CVE-2024-30051

Memory Safety in Microsoft Windows 10 1507 ≤ 10.0.10240.20651

CISA KEVActive ExploitationEUVD ExploitedRansomware-linkedMemory Safety
Published
14 May 2024
Modified
28 October 2025
KEV Added
14 May 2024
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.057 92th percentile
Risk Priority 83 floored blend · peak EPSS

Summary

CVE-2024-30051 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Microsoft Windows 10 1507. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 8% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-30051 is an elevation of privilege vulnerability in the Windows DWM Core Library stemming from a heap-based buffer overflow (CWE-122) and out-of-bounds write (CWE-787). The flaw affects the Desktop Window Manager component on supported Windows versions and carries a CVSS 3.1 score of 7.8 reflecting local attack vector, low complexity, and low required privileges.

A local attacker with a low-privileged account can exploit the issue without user interaction to execute arbitrary code with elevated privileges, potentially gaining full control over confidentiality, integrity, and availability on the affected system.

Microsoft's advisory at msrc.microsoft.com directs administrators to apply the security updates released on May 14, 2024. The vulnerability is also listed in CISA's Known Exploited Vulnerabilities catalog, confirming active exploitation in the wild and requiring prioritized remediation.

EPSS scores have reached a peak of 0.5658 with a current value of 0.5093, indicating sustained exploitation interest following disclosure.

EU & UK References

Vulnerability Data

Windows DWM Core Library Elevation of Privilege Vulnerability

CWE(s)
KEV Date Added
14 May 2024

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-36036Same product: Microsoft Windows 10 1507both on KEV
CVE-2023-23376Same product: Microsoft Windows 10 1507both on KEV
CVE-2023-28252Same product: Microsoft Windows 10 1507both on KEV
CVE-2022-41125Same product: Microsoft Windows 10 1507both on KEV
CVE-2024-38065Same product: Microsoft Windows 10 1507
CVE-2022-41073Same product: Microsoft Windows 10 1507both on KEV
CVE-2022-41128Same product: Microsoft Windows 10 1507both on KEV
CVE-2024-38060Same product: Microsoft Windows 10 1507
CVE-2024-38051Same product: Microsoft Windows 10 1507
CVE-2024-38054Same product: Microsoft Windows 10 1507

Affected Assets

microsoft
windows 10 1507
≤ 10.0.10240.20651 · ≤ 10.0.10240.20651
microsoft
windows 10 1607
≤ 10.0.14393.6981 · ≤ 10.0.14393.6981
microsoft
windows 10 1809
≤ 10.0.17763.5820
microsoft
windows 10 21h2
≤ 10.0.19044.4412
microsoft
windows 10 22h2
≤ 10.0.19045.4412
microsoft
windows 11 21h2
≤ 10.0.22000.2960
microsoft
windows 11 22h2
≤ 10.0.22621.3593
microsoft
windows 11 23h2
≤ 10.0.22631.3593
microsoft
windows server 2016
≤ 10.0.14393.6981
microsoft
windows server 2019
≤ 10.0.17763.5820
+1 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.4.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (including fuzzing and memory-error detectors) can discover heap overflows after they have been coded.

Input validation enforces bounds checking on data written to heap buffers, directly stopping the overflow condition from being introduced.

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

Security engineering principles require use of memory-safe constructs and bounds-checked allocation routines that avoid introducing heap overflows.

Memory-protection mechanisms limit the ability of a heap overflow to execute attacker-controlled code or corrupt adjacent structures.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.

PR.PS-02 partial match
prevents

Timely patching removes known heap-overflow instances after they exist.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development and acceptance can detect heap overflows before release.

prevents

Secure development lifecycle mandates practices that reduce the likelihood of introducing heap overflows.

prevents

Application security requirements can specify bounds-checking and safe memory APIs that mitigate heap overflows.

prevents

Secure architecture and engineering principles include memory-safety and input-validation controls that address heap overflows.

prevents

Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.

prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References