Skip to content
Server Security Center
KEVhigh7.8

CVE-2012-0151: Microsoft Windows Authenticode Signature Verification Remote Code Execution

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-06-08.

CVSS v3.1 (CISA ADP)
7.8
high
EPSS (exploit probability, 30 days)
88%
higher than 99.7% of all CVEs
Added to CISA KEV
2022-06-08
US federal due date 2022-06-22
Automatable (CISA SSVC)
no
technical impact: total

CVE-2012-0151 explained

CVE-2012-0151 is a flaw in the Authenticode Signature Verification function (WinVerifyTrust) in Microsoft Windows. It does not properly validate the digest of a signed portable executable (PE) file, so a modified file with additional content can still appear validly signed. CISA lists it as known to be exploited, which makes patching a priority.

Impact

An attacker who convinces a user to open or run a modified signed PE file can execute arbitrary code. The attack is local and requires user interaction, but no privileges. Successful exploitation can fully compromise confidentiality, integrity and availability. CISA rates the technical impact as total and the attack as not automatable. Attackers are known to use this vulnerability. Known ransomware use is listed as unknown.

Who is affected

The description names 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. The structured CVE record lists no affected version ranges for Microsoft Windows. It also names no fixed version. Check the Microsoft security advisory for the updates that apply to each Windows version.

Written with AI from the data on this page and checked against it automatically.

Official description

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."

CISA required action: Apply updates per vendor instructions.

CISA notes

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: docs.microsoft.com/en-us/security-updates/securitybulleti…
  • CISA's deadline for US federal agencies: 2022-06-22 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply the Microsoft security updates for this vulnerability on all affected Windows systems, following the vendor advisory.
  2. Follow CISA's required action: apply updates per vendor instructions.
  3. Replace or upgrade Windows versions that no longer receive Microsoft updates.
  4. Warn users not to run executables from untrusted sources, even if they appear validly signed.
  5. Check systems for signs of compromise, such as unexpected signed executables or unusual processes.

The CVE record names no fixed version, but this does not mean no fix exists. Consult the Microsoft security advisory for the updates for your Windows version and apply them, as CISA's required action states. Until updates are installed, limit execution of files from untrusted sources and do not rely on Authenticode signatures alone to trust executables.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-20 Improper Input Validation

Questions about CVE-2012-0151

Is CVE-2012-0151 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-06-08, with a US federal due date of 2022-06-22. Whether it has been used in ransomware campaigns is listed as unknown.
Can it be exploited without user action?
No. The attack requires user interaction, such as a user running a modified signed file. CISA rates it as not automatable. No privileges are required.
Why does a valid-looking signature matter here?
The flaw lets a signed PE file with added content still pass signature checks. Users and tools that trust the signature may run modified code, which can lead to full system compromise.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.