CVE-2018-8120
Microsoft Win32k Privilege Escalation Vulnerability
Microsoft Win32k
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in memory, aka "Win32k Elevation of Privilege Vulnerability." This affects Windows Server 2008, Windows 7, Windows Server 2008 R2. This CVE ID is unique from CVE-2018-8124, CVE-2018-8164, CVE-2018-8166.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 15 March 2022. US federal agencies were required to remediate it by 5 April 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 73.3%, which is higher than 99.5% 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:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2018-8120 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2018-8120.
What does CVE-2018-8120 affect?
CVE-2018-8120 affects Microsoft Win32k. An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in memory, aka "Win32k Elevation of Privilege Vulnerability." This affects Windows Server 2008, Windows 7, Windows Server 2008 R2. This CVE ID is unique from CVE-2018-8124, CVE-2018-8164, CVE-2018-8166.
How severe is CVE-2018-8120?
CVE-2018-8120 is rated HIGH with a CVSS base score of 7. EPSS puts the probability of exploitation in the next 30 days at 73.3%, higher than 99.5% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 5 April 2022.
How should organisations respond to CVE-2018-8120?
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.