Live › vulnerability › CVE-2012-0151
Go to dashboardWindows Authenticode signature verification (WinVerifyTrust) does not properly check the digest of signed PE files, so a crafted signed executable can pass as validly signed. An attacker who gets a user to open such a file can run code on the machine.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply updates per vendor instructions.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Microsoft Windows | vendor | – | – |
| microsoft windows 7 | vendor | – | – |
| microsoft windows server 2003 | vendor | – | – |
| microsoft windows server 2008 | vendor | – | – |
| microsoft windows server 2008 | vendor | = r2 | – |
| microsoft windows vista | vendor | – | – |
| microsoft windows xp | vendor | – | – |
Unknown from the sources.
Apply the Microsoft security update for CVE-2012-0151 per vendor instructions (CISA KEV required action).
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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."
This page as .md · .json · in your agent: get_signal("CVE-2012-0151")
CISA KEV catalog, Creative Commons 0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.