dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Sep 2024.
Windows 10 1507Operating system · Microsoft

CVE-2024-38107

HIGH · 7.8 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 10.0.10240.20751 / 10.0.14393.7259 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Windows Power Dependency Coordinator Elevation of Privilege Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Windows Power Dependency Coordinator Elevation of Privilege vulnerability (CVSS 7.8) enabling a local attacker to escalate privileges on affected Windows systems.

MitigationApply the Microsoft security update for CVE-2024-38107 through Windows Update or enterprise patch management systems, then verify successful installation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20751
Windows 10 1607Operating system
Affected:< 10.0.14393.7259
Windows 10 1809Operating system
Affected:< 10.0.17763.6189
Windows 10 21h2Operating system
Affected:< 10.0.19044.4780
Windows 10 22h2Operating system
Affected:< 10.0.19045.4780
Windows 11 21h2Operating system
Affected:< 10.0.22000.3147
Windows 11 22h2Operating system
Affected:< 10.0.22621.4037
Windows 11 23h2Operating system
Affected:< 10.0.22631.4037

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows build number
    Affected if The build number falls below any of these thresholds: 10240.20751 (1507), 14393.7259 (1607), 17763.6189 (1809), 19044.4780 (21h2/22h2), 22000.3147 (Win11 21h2), 22621.4037 (Win11 22h2), or 22631.4037 (Win11 23h2)
  2. Verify Power Dependency Coordinator component presence
    Check the registry key 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages' for any package containing 'PowerDependencyCoordinator' or query via PowerShell: 'Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like "*PowerDependencyCoordinator*"}'
    Affected if The Power Dependency Coordinator component is installed on the system
  3. Confirm authenticated user context
    Review system user accounts and groups using 'net user' or 'Get-LocalUser' to identify which users have local account access
    Affected if An attacker with any authenticated user account can potentially exploit this vulnerability to escalate to SYSTEM privileges

The system is affected if it runs a Windows version with a build number below the thresholds listed AND has the Power Dependency Coordinator component installed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20751 / 10.0.14393.7259 / 10.0.17763.6189 or later
Fixed in 10.0.10240.2075110.0.14393.725910.0.17763.6189
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update for CVE-2024-38107 through Windows Update or enterprise patch management systems, then verify successful installation.

Recommended fix High confidence

Upgrade to the specific build number for your Windows version as listed in the June 2024 Security Updates (KB5039803 or subsequent releases)

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which version range applies (Windows 10 1507, 1607, 1809, 21h2, 22h2 or Windows 11 21h2, 22h2, 23h2)
  3. Obtain the appropriate cumulative update for your Windows version from Microsoft Update Catalog or Windows Update
  4. Apply the security update matching your fixed build version: 10.0.10240.20751 (Win10 1507), 10.0.14393.7259 (Win10 1607), 10.0.17763.6189 (Win10 1809), 10.0.19044.4780 (Win10 21h2), 10.0.19045.4780 (Win10 22h2), 10.0.22000.3147 (Win11 21h2), 10.0.22621.4037 (Win11 22h2), or 10.0.22631.4037 (Win11 23h2)
  5. Restart the system after applying the update
  6. Verify the update was installed successfully by checking Windows Update history or running 'winver' to confirm the build number matches the fixed version
Caveat Standard Windows cumulative update considerations apply - review backup procedures and ensure compatibility with critical applications before deployment in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38107 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-38107 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data