Microsoft Windows Privilege Escalation
CVE-2019-1215 is a high-severity improper privilege management vulnerability in Windows from Microsoft, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Windows versions: 7 for 32-bit Systems Service Pack 1; 7 for x64-based Systems Service Pack 1; 8.1 for 32-bit systems, and others listed below. The record does not name a fixed version, so check the vendor advisory. CISA added it to the Known Exploited Vulnerabilities catalogue on November 3, 2021, which means attacks have been observed in the wild, including in ransomware campaigns.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Check which version of Windows you run against the affected versions below, and install the vendor's latest release.
- CISA's required action: Apply updates per vendor instructions.
- Read the advisory on portal.msrc.microsoft.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Windows | 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; and 12 more ranges | Not stated |
| Microsoft | Windows Server | 2008 R2 for Itanium-Based Systems Service Pack 1; 2008 R2 for x64-based Systems Service Pack 1; 2008 for 32-bit Systems Service Pack 2 (Core installation); 2012; 2012 (Core installation); 2012 R2; 2012 R2 (Core installation); 2016; and 7 more ranges | Not stated |
| Microsoft | Windows 10 Version 1903 for 32-bit Systems | Not specified in the record | Not stated |
| Microsoft | Windows 10 Version 1903 for x64-based Systems | Not specified in the record | Not stated |
| Microsoft | Windows 10 Version 1903 for ARM64-based Systems | Not specified in the record | Not stated |
| Microsoft | Windows Server, version 1903 (Server Core installation) | Not specified in the record | Not stated |
| Microsoft | Windows 10 1507 | Not specified in the record | Not stated |
| Microsoft | Windows 10 1607 | Not specified in the record | Not stated |
| Microsoft | Windows 10 1703 | Not specified in the record | Not stated |
| Microsoft | Windows 10 1709 | Not specified in the record | Not stated |
| Microsoft | Windows 10 1803 | Not specified in the record | Not stated |
| Microsoft | Windows 10 1809 | Not specified in the record | Not stated |
| Microsoft | Windows 10 1903 | Not specified in the record | Not stated |
| Microsoft | Windows 7 | Not specified in the record | Not stated |
| Microsoft | Windows 8.1 | Not specified in the record | Not stated |
| Microsoft | Windows Rt 8.1 | Not specified in the record | Not stated |
| Microsoft | Windows Server 1803 | Not specified in the record | Not stated |
| Microsoft | Windows Server 1903 | Not specified in the record | Not stated |
| Microsoft | Windows Server 2008 | r2 | Not stated |
| Microsoft | Windows Server 2012 | r2 | Not stated |
| Microsoft | Windows Server 2016 | Not specified in the record | Not stated |
| Microsoft | Windows Server 2019 | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 3.1 | 7.8 | High | CISA (ADP) |
| CVSS 2.0 | 7.2 | High | NVD |
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Privilege Management
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Follow the principle of least privilege when assigning access rights to entities in a software system.
- Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
More Improper Privilege Management vulnerabilities (CWE-269)
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-1215US Government Resource
Other vulnerabilities in Windows
- 7.4 High severity
- 7.4 High severity
- 7.8 High severity
- 7.5 High severity
- 7.0 High severity
- 7.8 High severity
Recent Improper Privilege Management vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
Microsoft Windows Privilege Escalation Exploited
Spotted an error? Tell us.