Skip to content
Server Security Center
KEVhigh7.8

CVE-2024-38107: Microsoft Windows Power Dependency Coordinator Privilege Escalation

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2024-08-13.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
1.6%
higher than 76.9% of all CVEs
Added to CISA KEV
2024-08-13
US federal due date 2024-09-03
Automatable (CISA SSVC)
no
technical impact: total

CVE-2024-38107 explained

CVE-2024-38107 is a use-after-free vulnerability in the Microsoft Windows Power Dependency Coordinator. It lets a local attacker escalate privileges to SYSTEM. CISA lists it as known to be exploited, so affected Windows client and server systems should be patched promptly.

Impact

An attacker who can already run code on a system with low privileges can gain SYSTEM privileges without user interaction. That gives full control over confidentiality, integrity and availability of the affected machine. CISA rates the technical impact as total and the vulnerability as not automatable, so exploitation requires local access per target. Attackers are known to exploit it. Whether it has been used in ransomware campaigns is unknown.

Who is affected

The CVE record lists Windows 10 Versions 1507, 1809, 21H2 and 22H2, Windows 11 versions 21H2, 22H2, 22H3 and 23H2, Windows Server 2019 (including Server Core installation), Windows Server 2022, and Windows Server 2022, 23H2 Edition (Server Core installation). Fixed builds include 10.0.17763.6189 (1809/Server 2019), 10.0.20348.2655 (Server 2022), 10.0.19044.4780 and 10.0.19045.4780 (Windows 10 21H2/22H2), 10.0.22000.3147, 10.0.22621.4037 and 10.0.22631.4037 (Windows 11), 10.0.25398.1085 and 10.0.10240.20751. Further products are listed on this page.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft Windows Power Dependency Coordinator contains an unspecified vulnerability that allows for privilege escalation, enabling a local attacker to obtain SYSTEM privileges.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.6189
    Fixed in
    • 10.0.17763.6189
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.6189
    Fixed in
    • 10.0.17763.6189
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.6189
    Fixed in
    • 10.0.17763.6189
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.2655
    Fixed in
    • 10.0.20348.2655
  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    • < 10.0.22000.3147
    Fixed in
    • 10.0.22000.3147
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.4780
    Fixed in
    • 10.0.19044.4780
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.4037
    Fixed in
    • 10.0.22621.4037
  • Microsoft Windows 10 Version 22H2x64, ARM64, 32-bit
    Affected
    • < 10.0.19045.4780
    Fixed in
    • 10.0.19045.4780
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.4037
    Fixed in
    • 10.0.22631.4037
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.4037
    Fixed in
    • 10.0.22631.4037
Show 10 more products
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1085
    Fixed in
    • 10.0.25398.1085
  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.20751
    Fixed in
    • 10.0.10240.20751
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.7259
    Fixed in
    • 10.0.14393.7259
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.7259
    Fixed in
    • 10.0.14393.7259
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.7259
    Fixed in
    • 10.0.14393.7259
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25031
    Fixed in
    • 6.2.9200.25031
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25031
    Fixed in
    • 6.2.9200.25031
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22134
    Fixed in
    • 6.3.9600.22134
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22134
    Fixed in
    • 6.3.9600.22134
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.1457
    Fixed in
    • 10.0.26100.1457

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1809: 10.0.17763.6189
    • Microsoft Windows Server 2019: 10.0.17763.6189
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.6189
    • Microsoft Windows Server 2022: 10.0.20348.2655
    • Microsoft Windows 11 version 21H2: 10.0.22000.3147
    • Microsoft Windows 10 Version 21H2: 10.0.19044.4780
    Fixed versions for 14 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38107
  • CISA's deadline for US federal agencies: 2024-09-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to the fixed build listed for its Windows version.
  2. Prioritize servers and multi-user systems where low-privileged users or services can run code locally.
  3. Verify installed build numbers across the fleet to confirm the update applied everywhere.
  4. Follow the Microsoft advisory for any additional guidance and apply mitigations per vendor instructions, as CISA requires.
  5. Review systems for signs of compromise, such as unexpected SYSTEM-level processes or new privileged accounts.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-416 Use After Free

Questions about CVE-2024-38107

Can this be exploited remotely?
No. The attack vector is local. An attacker needs low-privileged access to the system first, then can escalate to SYSTEM without user interaction.
Is this vulnerability being exploited?
Yes. CISA added CVE-2024-38107 to its Known Exploited Vulnerabilities catalog on 2024-08-13, with a US federal due date of 2024-09-03. Known ransomware use is listed as unknown.
Which build fixes Windows Server 2022?
The CVE record names 10.0.20348.2655 as the fixed build for Windows Server 2022, and 10.0.25398.1085 for Windows Server 2022, 23H2 Edition (Server Core installation).

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.