CVE-2019-1322: Microsoft Windows Privilege Escalation
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-15.
- CVSS v3.1 (CISA ADP)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 19%
- higher than 97.3% of all CVEs
- Added to CISA KEV
- 2022-03-15
- US federal due date 2022-04-05
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2019-1322 explained
CVE-2019-1322 is an elevation of privilege vulnerability in Microsoft Windows that occurs when Windows improperly handles authentication requests. It matters because CISA lists it as known exploited, including known use in ransomware campaigns, and successful exploitation gives total control of the affected system.
Impact
A local attacker who already has low-privileged access can elevate privileges without any user interaction, gaining high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. Exploitation is not considered automatable at scale, but attackers are known to use this vulnerability, including in ransomware activity.
Who is affected
The CVE record lists Microsoft Windows 10 Version 1803 and Version 1809 (32-bit, x64-based and ARM64-based Systems). It also lists Microsoft Windows Server 2019, 2019 (Core installation) and version 1803 (Core Installation). Windows 10 Version 1903 (32-bit, x64-based, ARM64-based) and Windows Server, version 1903 (Server Core installation) appear as product entries without version details. The CVE record names no fixed version.
Written with AI from the data on this page and checked against it automatically.
Official description
An elevation of privilege vulnerability exists when Windows improperly handles authentication requests, aka 'Microsoft Windows Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2019-1320, CVE-2019-1340.
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 WindowsAffectedFixed in
- 10 Version 1803 for 32-bit Systems
- 10 Version 1803 for x64-based Systems
- 10 Version 1803 for ARM64-based Systems
- 10 Version 1809 for 32-bit Systems
- 10 Version 1809 for x64-based Systems
- 10 Version 1809 for ARM64-based Systems
not statedVersion statement as published by the CNA (free text).
- Microsoft Windows ServerAffectedFixed in
- 2019
- 2019 (Core installation)
- version 1803 (Core Installation)
not stated - Microsoft Windows 10 Version 1903 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1903 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1903 for ARM64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows Server, version 1903 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft WindowsVersion statement as published by the CNA (free text). |
| not stated |
| Microsoft Windows Server |
| not stated |
| Microsoft Windows 10 Version 1903 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1903 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1903 for ARM64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows Server, version 1903 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
- CISA's deadline for US federal agencies: 2022-04-05 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security updates for CVE-2019-1322 as described in the vendor advisory.
- Follow CISA's required action: apply updates per vendor instructions.
- Prioritize patching systems where untrusted or low-privileged users can log on locally.
- Check systems for signs of compromise, given known exploitation and ransomware use.
- Upgrade or replace Windows versions that no longer receive security updates.
The CVE record names no fixed version, which does not mean no fix exists. Consult the Microsoft advisory to identify the update for each affected Windows version and follow CISA's required action to apply updates per vendor instructions. Until updated, limit local logon rights and monitor for privilege escalation activity.
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-2019-1322
- Is CVE-2019-1322 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-15 and notes known use in ransomware campaigns. The US federal due date was 2022-04-05.
- Can it be exploited remotely?
- The CVSS vector lists a local attack vector. An attacker needs low-privileged access to the system but no user interaction to elevate privileges.
- Which fixed version should I install?
- The CVE record names no fixed version. Use the Microsoft advisory to find the correct security update for your Windows version and apply it.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
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.