CVE-2016-0151
Microsoft Windows CSRSS Security Feature Bypass Vulnerability
Microsoft Client-Server Run-time Subsystem (CSRSS)
The Client-Server Run-time Subsystem (CSRSS) in Microsoft Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, and Windows 10 Gold and 1511 mismanages process tokens, which allows local users to gain privileges via a crafted application, aka "Windows CSRSS Security Feature Bypass Vulnerability."
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 28 March 2022. US federal agencies were required to remediate it by 18 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 62.9%, which is higher than 99.2% 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:N/UI:R/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2016-0151 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2016-0151.
What does CVE-2016-0151 affect?
CVE-2016-0151 affects Microsoft Client-Server Run-time Subsystem (CSRSS). The Client-Server Run-time Subsystem (CSRSS) in Microsoft Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, and Windows 10 Gold and 1511 mismanages process tokens, which allows local users to gain privileges via a crafted application, aka "Windows CSRSS Security Feature Bypass Vulnerability."
How severe is CVE-2016-0151?
CVE-2016-0151 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 62.9%, higher than 99.2% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 18 April 2022.
How should organisations respond to CVE-2016-0151?
Apply the vendor patch for Microsoft Client-Server Run-time Subsystem (CSRSS) 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.