CVE-2017-0263
Microsoft Win32k Privilege Escalation Vulnerability
Microsoft Win32k
The kernel-mode drivers in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allow local users to gain privileges via a crafted application, aka "Win32k Elevation of Privilege Vulnerability."
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 10 February 2022. US federal agencies were required to remediate it by 10 August 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 10%, which is higher than 95.7% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2017-0263 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2017-0263.
What does CVE-2017-0263 affect?
CVE-2017-0263 affects Microsoft Win32k. The kernel-mode drivers in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allow local users to gain privileges via a crafted application, aka "Win32k Elevation of Privilege Vulnerability."
How severe is CVE-2017-0263?
CVE-2017-0263 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 10%, higher than 95.7% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 10 August 2022.
How should organisations respond to CVE-2017-0263?
Apply the vendor patch for Microsoft Win32k as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.