CVE-2012-0151
Microsoft Windows Authenticode Signature Verification Remote Code Execution Vulnerability
Microsoft Windows
The Authenticode Signature Verification function in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, R2, and R2 SP1, Windows 7 Gold and SP1, and Windows 8 Consumer Preview does not properly validate the digest of a signed portable executable (PE) file, which allows user-assisted remote attackers to execute arbitrary code via a modified file with additional content, aka "WinVerifyTrust Signature Validation Vulnerability."
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 8 June 2022. US federal agencies were required to remediate it by 22 June 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 87.7%, which is higher than 99.8% 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-2012-0151 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2012-0151.
What does CVE-2012-0151 affect?
CVE-2012-0151 affects Microsoft Windows. The Authenticode Signature Verification function in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, R2, and R2 SP1, Windows 7 Gold and SP1, and Windows 8 Consumer Preview does not properly validate the digest of a signed portable executable (PE) file, which allows user-assisted remote attackers to execute arbitrary code via a modified file with additional content, aka "WinVerifyTrust Signature Validation Vulnerability."
How severe is CVE-2012-0151?
CVE-2012-0151 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 87.7%, higher than 99.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 22 June 2022.
How should organisations respond to CVE-2012-0151?
Apply the vendor patch for Microsoft Windows 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.