Skip to content
Server Security Center
KEVhigh7.8

CVE-2024-38014: Microsoft Windows Installer Improper Privilege Management

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

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

CVE-2024-38014 explained

CVE-2024-38014 is an improper privilege management vulnerability (CWE-269) in Microsoft Windows Installer. It could allow an attacker to gain SYSTEM privileges on affected Windows client and server versions. CISA lists it as known to be exploited, so affected systems should be patched promptly.

Impact

An attacker who already has local access with low privileges can gain SYSTEM privileges without any user interaction. This gives high impact on confidentiality, integrity and availability of the affected system. CISA rates the technical impact as total, meaning full control of the component. CISA does not rate it as automatable, so exploitation requires manual steps per target. Attackers are known to use this vulnerability; ransomware use is listed as unknown.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 21H2 and 22H2, Windows 11 versions 21H2, 22H2, 22H3, 23H2 and 24H2, Windows Server 2008 Service Pack 2 and Windows Server 2008 R2 Service Pack 1. Fixed builds include 10.0.10240.20766, 10.0.14393.7336, 10.0.17763.6293, 10.0.19044.4894, 10.0.19045.4894, 10.0.22000.3197, 10.0.22621.4169, 10.0.22631.4169, 10.0.26100.1742, 6.0.6003.22870 and 6.1.7601.27320. 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 Installer contains an improper privilege management vulnerability that could allow an attacker to gain 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 150732-bit, x64
    Affected
    • < 10.0.10240.20766
    Fixed in
    • 10.0.10240.20766
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.7336
    Fixed in
    • 10.0.14393.7336
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.6293
    Fixed in
    • 10.0.17763.6293
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.4894
    Fixed in
    • 10.0.19044.4894
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.4894
    Fixed in
    • 10.0.19045.4894
  • Microsoft Windows 11 version 21H2ARM64, x64
    Affected
    • < 10.0.22000.3197
    Fixed in
    • 10.0.22000.3197
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.4169
    Fixed in
    • 10.0.22621.4169
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.4169
    Fixed in
    • 10.0.22631.4169
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.4169
    Fixed in
    • 10.0.22631.4169
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.1742
    Fixed in
    • 10.0.26100.1742
Show 14 more products
  • Microsoft Windows Server 2008 Service Pack 2x64, 32-bit
    Affected
    • < 6.0.6003.22870
    Fixed in
    • 6.0.6003.22870
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27320
    Fixed in
    • 6.1.7601.27320
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27320
    Fixed in
    • 6.1.7601.27320
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.22870
    Fixed in
    • 6.0.6003.22870
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25073
    Fixed in
    • 6.2.9200.25073
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25073
    Fixed in
    • 6.2.9200.25073
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22175
    Fixed in
    • 6.3.9600.22175
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22175
    Fixed in
    • 6.3.9600.22175
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.7336
    Fixed in
    • 10.0.14393.7336
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.7336
    Fixed in
    • 10.0.14393.7336
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.6293
    Fixed in
    • 10.0.17763.6293
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.6293
    Fixed in
    • 10.0.17763.6293
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.2700
    Fixed in
    • 10.0.20348.2700
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1128
    Fixed in
    • 10.0.25398.1128

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.20766
    • Microsoft Windows 10 Version 1607: 10.0.14393.7336
    • Microsoft Windows 10 Version 1809: 10.0.17763.6293
    • Microsoft Windows 10 Version 21H2: 10.0.19044.4894
    • Microsoft Windows 10 Version 22H2: 10.0.19045.4894
    • Microsoft Windows 11 version 21H2: 10.0.22000.3197
    Fixed versions for 18 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38014
  • CISA's deadline for US federal agencies: 2024-10-01 (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 systems where many users have local or remote logon rights, such as terminal servers and shared workstations.
  3. Follow the Microsoft advisory for product-specific update packages and guidance.
  4. Limit local logon rights and remove unnecessary low-privilege accounts on sensitive systems.
  5. Check for signs of compromise, such as unexpected SYSTEM-level processes or new privileged accounts, on systems patched late.

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-269 Improper Privilege Management

Questions about CVE-2024-38014

Can this be exploited remotely?
No. The attack vector is local and requires low privileges. An attacker must already be able to run code on the system, for example through a compromised user account, before escalating to SYSTEM.
Is this vulnerability being exploited?
Yes. CISA added CVE-2024-38014 to its Known Exploited Vulnerabilities catalog on 2024-09-10, with a US federal due date of 2024-10-01. Whether it is used in ransomware campaigns is listed as unknown.
What does CISA require?
CISA's required action is to apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. For the listed Windows versions, the CVE record names fixed builds.

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.