Skip to content
Server Security Center
KEVhigh7.8

CVE-2021-34484: Microsoft Windows User Profile Service Privilege Escalation

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-31.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
22%
higher than 97.7% of all CVEs
Added to CISA KEV
2022-03-31
US federal due date 2022-04-21
Automatable (CISA SSVC)
no
technical impact: total

CVE-2021-34484 explained

CVE-2021-34484 is a privilege escalation vulnerability in the Microsoft Windows User Profile Service (CWE-269, improper privilege management). It affects many Windows client and server versions. CISA lists it as known to be exploited, so unpatched systems face a real risk.

Impact

An attacker who already has low-privileged local access can raise their privileges without any user interaction. A successful attack has high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so exploitation is not expected at scale without manual steps. Attackers are known to use the vulnerability. Whether ransomware groups use it is unknown.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 1909, 2004, 20H2 and 21H1, Windows 7, Windows 7 Service Pack 1, Windows 8.1, and Windows Server 2008 R2 Service Pack 1, including Server Core. Fixed builds include 10.0.10240.19022 (1507), 10.0.14393.4583 (1607), 10.0.17763.2114 (1809), 10.0.18363.1734 (1909), 10.0.19041.1165 (2004), 10.0.19042.1165 (20H2), 10.0.19043.1165 (21H1), 6.3.9600.20094 (8.1) and 6.1.7601.25685 (Windows 7, Server 2008 R2). The page lists 12 further products.

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

Official description

Microsoft Windows User Profile Service contains an unspecified vulnerability that allows for privilege escalation.

CISA required action: Apply updates per vendor instructions.

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.19022
    Fixed in
    • 10.0.10240.19022
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.4583
    Fixed in
    • 10.0.14393.4583
  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.2114
    Fixed in
    • 10.0.17763.2114
  • Microsoft Windows 10 Version 190932-bit, ARM64, x64
    Affected
    • < 10.0.18363.1734
    Fixed in
    • 10.0.18363.1734
  • Microsoft Windows 10 Version 200432-bit, ARM64, x64
    Affected
    • < 10.0.19041.1165
    Fixed in
    • 10.0.19041.1165
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.1165
    Fixed in
    • 10.0.19042.1165
  • Microsoft Windows 10 Version 21H132-bit, ARM64, x64
    Affected
    • < 10.0.19043.1165
    Fixed in
    • 10.0.19043.1165
  • Microsoft Windows 732-bit
    Affected
    • < 6.1.7601.25685
    Fixed in
    • 6.1.7601.25685
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • < 6.1.7601.25685
    Fixed in
    • 6.1.7601.25685
  • Microsoft Windows 8.132-bit, ARM64, x64
    Affected
    • < 6.3.9600.20094
    Fixed in
    • 6.3.9600.20094
Show 14 more products
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.25685
    Fixed in
    • 6.1.7601.25685
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.25685
    Fixed in
    • 6.1.7601.25685
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.21192
    Fixed in
    • 6.0.6003.21192
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.21192
    Fixed in
    • 6.0.6003.21192
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.23435
    Fixed in
    • 6.2.9200.23435
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.23435
    Fixed in
    • 6.2.9200.23435
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.20094
    Fixed in
    • 6.3.9600.20094
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.20094
    Fixed in
    • 6.3.9600.20094
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.4583
    Fixed in
    • 10.0.14393.4583
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.4583
    Fixed in
    • 10.0.14393.4583
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.2114
    Fixed in
    • 10.0.17763.2114
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.2114
    Fixed in
    • 10.0.17763.2114
  • Microsoft Windows Server version 2004x64
    Affected
    • < 10.0.19041.1165
    Fixed in
    • 10.0.19041.1165
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1165
    Fixed in
    • 10.0.19042.1165

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.19022
    • Microsoft Windows 10 Version 1607: 10.0.14393.4583
    • Microsoft Windows 10 Version 1809: 10.0.17763.2114
    • Microsoft Windows 10 Version 1909: 10.0.18363.1734
    • Microsoft Windows 10 Version 2004: 10.0.19041.1165
    • Microsoft Windows 10 Version 20H2: 10.0.19042.1165
    Fixed versions for 18 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2021-34484
  • CISA's deadline for US federal agencies: 2022-04-21 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply Microsoft's security updates per the vendor advisory, as CISA's required action states.
  2. Confirm each system runs at least the fixed build listed for its Windows version, for example 10.0.19043.1165 for Windows 10 21H1.
  3. Prioritize systems where many users have local or interactive access.
  4. Limit local logon rights and reduce the number of low-privileged accounts on sensitive systems.
  5. Check systems for signs of compromise, such as unexpected privileged accounts or privilege changes.

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

Questions about CVE-2021-34484

Can this be exploited remotely?
No. The attack vector is local. An attacker needs low-privileged access to the system first, and no user interaction is required.
Is this vulnerability being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-31, with a US federal due date of 2022-04-21. Whether ransomware groups use it is unknown.
What is the required action?
CISA requires applying updates per vendor instructions. Install Microsoft's updates so each system reaches the fixed build listed for its version.

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.