Loading vulnerability…
CVE-2020-1599 is a Windows spoofing vulnerability involving improper verification of signed files, allowing attacker-controlled script content to be embedded within another file format while the file continues to appear validly signed. Reported abuse shows adversaries appending HTA/script content to signed Windows DLLs and then invoking that content through mshta.exe, effectively hiding malicious logic inside files that retain trust indicators associated with Authenticode-signed content. The weakness is closely associated with a gap in signature validation that permits additional content in the certificate or signature padding area without invalidating trust decisions, enabling execution of embedded HTA content from ostensibly legitimate signed files.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Vulnerability referenced in the context of mshta.exe abuse/LOLBIN tradecraft; detections expanded to catch suspicious mshta command lines using unusual file extensions.
A Windows code-signing related vulnerability referenced as part of ZLoader's execution chain to run a malicious script appended to a signed DLL.
A vulnerability referenced as part of ZLoader operators' defense-evasion techniques using validly signed files to hide malicious scripts.
Referenced as related to the long-standing Authenticode signature verification weakness enabling appended data while maintaining signature validity; the content does not provide additional technical detail beyond being part of the same known issue set.
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.