Loading vulnerability…
CVE-2012-0151 is a signature validation flaw in Microsoft Windows Authenticode handling. The vulnerability exists in the WinVerifyTrust/AuthentiCode signature verification logic on affected Windows versions because the digest of a signed portable executable file is not properly validated when additional content is appended. As a result, a specially modified PE file can retain an apparently valid digital signature even though attacker-controlled data has been added after signing. This weakness can be abused to make a tampered executable appear trustworthy to users or security controls that rely on Authenticode validation, enabling delivery of malicious content inside or alongside a signed file. The issue is user-assisted because successful exploitation depends on a target opening or executing the modified file.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability referenced as part of ZLoader operators' defense-evasion techniques using validly signed files to hide malicious scripts.
Referenced as an example in discussion of a digital signature verification vulnerability, but not specifically described as the vulnerability used in the campaign.
Referenced as related to the known Authenticode signature verification weakness (appending data to signed files while preserving apparent signature validity); the content does not add further specifics on this CVE’s mechanics.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.