CVE-2015-1701
Microsoft Win32k Privilege Escalation Vulnerability
Microsoft Win32k
Win32k.sys in the kernel-mode drivers in Microsoft Windows Server 2003 SP2, Vista SP2, and Server 2008 SP2 allows local users to gain privileges via a crafted application, as exploited in the wild in April 2015, aka "Win32k Elevation of Privilege Vulnerability."
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 3 March 2022. US federal agencies were required to remediate it by 24 March 2022. CISA records this vulnerability as known to be used in ransomware campaigns.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 56.2%, which is higher than 99.1% 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-2015-1701 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2015-1701.
What does CVE-2015-1701 affect?
CVE-2015-1701 affects Microsoft Win32k. Win32k.sys in the kernel-mode drivers in Microsoft Windows Server 2003 SP2, Vista SP2, and Server 2008 SP2 allows local users to gain privileges via a crafted application, as exploited in the wild in April 2015, aka "Win32k Elevation of Privilege Vulnerability."
How severe is CVE-2015-1701?
CVE-2015-1701 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 56.2%, higher than 99.1% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 24 March 2022.
How should organisations respond to CVE-2015-1701?
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.