CVE-2016-0162 is an information disclosure vulnerability in Microsoft Internet Explorer 9 through 11 that allows remote attackers to determine whether files exist on a victim's computer through crafted JavaScript. The Stegano exploit kit, also known as Astrum, used this vulnerability to identify analysis environments and security software before proceeding with a separate exploitation stage.
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.
An earlier vulnerability referenced as a variant ancestor of CVE-2019-0676 in Internet Explorer's handling of the res:// URI scheme.
A known Internet Explorer vulnerability used by the Stegano exploit kit chain to perform environment checks and anti-analysis verification before redirecting victims to the exploit landing page.
An Internet Explorer vulnerability abused by the Stegano exploit kit for anti-analysis checks. The malicious script checks for security products, packet-capture tools, sandboxing and virtualization software, and graphics drivers before allowing the attack to proceed.
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.