CVE-2019-1215: Microsoft Windows Privilege Escalation
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CISA ADP)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 19%
- higher than 97.4% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2019-1215 explained
CVE-2019-1215 is an elevation of privilege vulnerability in Microsoft Windows. It lies in the way ws2ifsl.sys (Winsock) handles objects in memory. CISA lists it as known exploited, with known ransomware use, so unpatched Windows and Windows Server systems are a priority for remediation.
Impact
An attacker who can already run code on a system with low privileges can elevate those privileges. No user interaction is needed. Successful exploitation gives high impact to confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected system. The attack is local and CISA does not consider it automatable. Attackers are known to exploit it, including in ransomware campaigns.
Who is affected
The CVE record lists Microsoft Windows, including 7 for 32-bit Systems Service Pack 1, 8.1 for x64-based systems, RT 8.1 and 10 Version 1607 for 32-bit Systems, with 12 more items shown on the page. It also lists Microsoft Windows Server editions: 13 listed models plus several Core installations such as version 1803 (Core Installation). Windows 10 Version 1903 (32-bit, x64, ARM64) and Windows Server, version 1903 (Server Core installation) are also listed. 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 in the way that ws2ifsl.sys (Winsock) handles objects in memory, aka 'Windows Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2019-1253, 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
- 7 for 32-bit Systems Service Pack 1
- 7 for x64-based Systems Service Pack 1
- 8.1 for 32-bit systems
- 8.1 for x64-based systems
- RT 8.1
- 10 for 32-bit Systems
- 10 for x64-based Systems
- 10 Version 1607 for 32-bit Systems
- 10 Version 1607 for x64-based Systems
- 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 stated - Microsoft Windows ServerAffectedFixed in
- 13 listed models (2008 for Itanium-Based Systems Service Pack 2 … 2019 (Core installation))
- 2008 R2 for x64-based Systems Service Pack 1 (Core installation)
- 2008 for 32-bit Systems Service Pack 2 (Core installation)
- version 1803 (Core Installation)
- 2008 for x64-based Systems Service Pack 2 (Core installation)
all 13 listed versions
- 2008 for Itanium-Based Systems Service Pack 2
- 2008 for x64-based Systems Service Pack 2
- 2008 for 32-bit Systems Service Pack 2
- 2008 R2 for Itanium-Based Systems Service Pack 1
- 2008 R2 for x64-based Systems Service Pack 1
- 2012
- 2012 (Core installation)
- 2012 R2
- 2012 R2 (Core installation)
- 2016
- 2016 (Core installation)
- 2019
- 2019 (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 Windows |
| not stated |
| Microsoft Windows Server |
all 13 listed versions
| 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-05-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security updates for CVE-2019-1215 as described in the vendor advisory.
- Prioritize patching, since CISA lists this vulnerability as known exploited with known ransomware use.
- Restrict local and remote logon rights so untrusted users cannot run code on affected systems.
- Check systems that went unpatched for signs of compromise, such as unexpected privileged accounts or processes.
- Replace Windows versions that no longer receive security updates.
The CVE record names no fixed version. This does not mean no fix exists. Follow the Microsoft advisory for the updates that apply to each Windows and Windows Server version. CISA's required action is to apply updates per vendor instructions. Until updates are in place, limit who can log on to affected systems 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
Weakness: CWE-269 Improper Privilege Management
Questions about CVE-2019-1215
- Can this be exploited remotely?
- No. The attack vector is local. An attacker needs low-privileged access to the system first, then can use the flaw to gain higher privileges. No user interaction is required.
- Is CVE-2019-1215 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03 and notes known ransomware use. The US federal due date was 2022-05-03.
- Which component is affected?
- The vulnerability is in ws2ifsl.sys (Winsock), which handles objects in memory improperly. Microsoft lists it as separate from CVE-2019-1253, CVE-2019-1278 and CVE-2019-1303.
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.