Threats / Microsoft / CVE-2024-38107
CVE-2024-38107
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Windows vulnerability
Microsoft Windows Power Dependency Coordinator privilege escalation vulnerability (CWE-416) allows local attackers to obtain SYSTEM privileges. Actively exploited in the wild.
Verdict
Today item — known-exploited.
A use-after-free flaw in Windows Power Dependency Coordinator enables local privilege escalation to SYSTEM level. The vulnerability is being actively exploited in real-world attacks, posing significant risk to Windows systems requiring immediate patching.
CISA KEV Yes · 2024-08-135EPSS 0.01635 (verify live)6CVSS 7.83CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
6 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-08-13).
Probability (EPSS)
EPSS 0.01635 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 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) · Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain initial access to a Windows system as a standard user through phishing, weak credentials, or another vector.
Business
An attacker establishes a foothold on corporate endpoints, bypassing initial access controls.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger the use-after-free condition in Power Dependency Coordinator to escalate my privileges to SYSTEM level.
Business
The attacker gains unrestricted control over the compromised system, enabling lateral movement and persistence.
3
Lateral reach — past segmentation narrative 3
Attacker
With SYSTEM privileges, I install malware, create backdoors, or exfiltrate sensitive data without detection.
Business
Critical business systems are compromised, leading to data breaches, operational disruption, and regulatory exposure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05