CVE-2019-1253: Microsoft Windows AppX Deployment Server 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)
- 12%
- higher than 96.1% 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-1253 explained
CVE-2019-1253 is an elevation of privilege vulnerability in the Windows AppX Deployment Server, which improperly handles junctions (link following). An attacker who already runs code on a system can gain higher privileges. CISA lists it as known exploited and notes known use in ransomware campaigns, so affected systems should be patched promptly.
Impact
An attacker must first gain code execution on the target system with low privileges. No user interaction is needed. Successful exploitation can give 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 each attack needs manual steps. Attackers are known to exploit it, including in ransomware campaigns.
Who is affected
The CVE record lists Microsoft Windows 10 versions 1703, 1709, 1803 and 1809 for various architectures (32-bit, x64, ARM64), with three further items shown on the page. It also lists Windows Server 2019, 2019 (Core installation) and version 1803 (Core Installation), Windows 10 Version 1903 for 32-bit, x64 and ARM64 systems, and Windows Server, version 1903 (Server Core installation). 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 the Windows AppX Deployment Server improperly handles junctions.To exploit this vulnerability, an attacker would first have to gain execution on the victim system, aka 'Windows Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2019-1215, CVE-2019-1278, CVE-2019-1303.
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 1703 for 32-bit Systems
- 10 Version 1703 for x64-based Systems
- 10 Version 1709 for 32-bit Systems
- 10 Version 1709 for x64-based Systems
- 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
- 10 Version 1709 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-1253 as described in the vendor advisory.
- Prioritize patching, since CISA lists this vulnerability as known exploited with known ransomware use.
- Limit who can run code on affected systems and restrict local accounts to reduce the chance of initial access.
- Check affected systems for signs of compromise, such as unexpected privileged accounts or processes.
- Upgrade Windows versions that no longer receive security updates to a supported release.
The CVE record names no fixed version. Follow the Microsoft advisory to identify the correct security update for each affected Windows release. CISA's required action is to apply updates per vendor instructions. Until updates are applied, restrict local access and code execution on affected systems and monitor for signs of compromise.
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-59 Improper Link Resolution Before File Access ('Link Following')
Questions about CVE-2019-1253
- Can this be exploited remotely?
- Not directly. The attack vector is local, and an attacker must first gain code execution on the victim system with low privileges. It is then used to raise privileges.
- Is this vulnerability being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-15 and notes known use in ransomware campaigns. US federal agencies had a due date of 2022-04-05.
- Which fixed version should I install?
- The CVE record names no fixed version. Use the Microsoft vendor advisory to find the security update for your Windows release, as CISA's required action directs.
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.