Skip to content
Server Security Center
KEVmedium5.2

CVE-2021-31199: Microsoft Enhanced Cryptographic Provider Privilege Escalation

Microsoft Enhanced Cryptographic Provider · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.

CVSS v3.1 (CVE record)
5.2
medium
EPSS (exploit probability, 30 days)
3.0%
higher than 87.6% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2021-11-17
Automatable (CISA SSVC)
no
technical impact: total

CVE-2021-31199 explained

CVE-2021-31199 is a privilege escalation vulnerability in the Microsoft Enhanced Cryptographic Provider on Windows. The record does not specify the flaw in detail. CISA lists it as known to be exploited by attackers, so affected Windows 10 and Windows Server systems should be updated promptly.

Impact

A local attacker who already has low-privileged access can escalate privileges without user interaction. The scope is changed, so the impact can reach beyond the vulnerable component. CVSS rates confidentiality and integrity impact as low, with no availability impact. CISA's assessment is that exploitation is not automatable, but the technical impact is total. Attackers are known to use this vulnerability. Ransomware use is listed as unknown.

Who is affected

The record lists Windows 10 versions 1507, 1607, 1809, 1909, 2004, 20H2 and 21H1, Windows Server 2016, Windows Server 2019 (including Server Core), and Windows Server versions 2004 and 20H2. Fixed builds include 10.0.17763.1999 (1809/Server 2019), 10.0.18363.1621 (1909), 10.0.19041.1052 (2004), 10.0.19042.1052 (20H2), 10.0.19043.1052 (21H1), 10.0.10240.18967 (1507) and 10.0.14393.4467 (1607/Server 2016). The page lists further products.

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

Official description

Microsoft Enhanced Cryptographic Provider 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 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.1999
    Fixed in
    • 10.0.17763.1999
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.1999
    Fixed in
    • 10.0.17763.1999
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.1999
    Fixed in
    • 10.0.17763.1999
  • Microsoft Windows 10 Version 190932-bit, x64, ARM64
    Affected
    • < 10.0.18363.1621
    Fixed in
    • 10.0.18363.1621
  • Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit
    Affected
    • < 10.0.19043.1052
    Fixed in
    • 10.0.19043.1052
  • Microsoft Windows 10 Version 200432-bit, ARM64, x64
    Affected
    • < 10.0.19041.1052
    Fixed in
    • 10.0.19041.1052
  • Microsoft Windows Server version 2004x64
    Affected
    • < 10.0.19041.1052
    Fixed in
    • 10.0.19041.1052
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.1052
    Fixed in
    • 10.0.19042.1052
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1052
    Fixed in
    • 10.0.19042.1052
  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.18967
    Fixed in
    • 10.0.10240.18967
Show 14 more products
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.4467
    Fixed in
    • 10.0.14393.4467
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.4467
    Fixed in
    • 10.0.14393.4467
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.4467
    Fixed in
    • 10.0.14393.4467
  • Microsoft Windows 732-bit
    Affected
    • < 6.1.7601.25632
    Fixed in
    • 6.1.7601.25632
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • < 6.1.7601.25632
    Fixed in
    • 6.1.7601.25632
  • Microsoft Windows 8.132-bit, x64, ARM64
    Affected
    • < 6.3.9600.20044
    • < 6.3.9600.20045
    Fixed in
    • 6.3.9600.20044
    • 6.3.9600.20045
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.21137
    Fixed in
    • 6.0.6003.21137
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.21137
    Fixed in
    • 6.0.6003.21137
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.25632
    Fixed in
    • 6.1.7601.25632
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.25632
    Fixed in
    • 6.1.7601.25632
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.23372
    Fixed in
    • 6.2.9200.23372
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.23372
    Fixed in
    • 6.2.9200.23372
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.20044
    • < 6.3.9600.20045
    Fixed in
    • 6.3.9600.20044
    • 6.3.9600.20045
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.20044
    • < 6.3.9600.20045
    Fixed in
    • 6.3.9600.20044
    • 6.3.9600.20045

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1809: 10.0.17763.1999
    • Microsoft Windows Server 2019: 10.0.17763.1999
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.1999
    • Microsoft Windows 10 Version 1909: 10.0.18363.1621
    • Microsoft Windows 10 Version 21H1: 10.0.19043.1052
    • Microsoft Windows 10 Version 2004: 10.0.19041.1052
    Fixed versions for 18 more products are in the table above.
  • Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
  • CISA's deadline for US federal agencies: 2021-11-17 (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. Verify the OS build number on every Windows 10 and Windows Server system after patching.
  3. Prioritize multi-user systems and servers, since the attack requires local, low-privileged access.
  4. Limit local and interactive logon rights to accounts that need them.
  5. Review systems for signs of compromise, such as unexpected privilege changes, given known exploitation.

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

Questions about CVE-2021-31199

Can this be exploited remotely?
No. According to the CVSS vector, the attack vector is local. The attacker needs low-privileged access to the system first, but no user interaction is required.
Why patch a medium-severity issue urgently?
CISA lists CVE-2021-31199 as known to be exploited and rates its technical impact as total. The required action is to apply updates per vendor instructions. The US federal due date was 2021-11-17.
Which build fixes Windows Server 2019?
Build 10.0.17763.1999 contains the fix for Windows Server 2019, including Server Core installations, and for Windows 10 Version 1809.

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.