Loading vulnerability…
CVE-2019-0676 is an information disclosure vulnerability in Microsoft Internet Explorer caused by improper handling of objects in memory during processing of the res:// URI scheme. The flaw is described as a variant of earlier Internet Explorer issues including CVE-2017-0022, CVE-2016-3298, CVE-2016-0162, and CVE-2016-3351. Successful exploitation allows an attacker to determine whether specific files are present on the victim system. The vulnerability does not itself provide code execution, but it can be used as a reconnaissance primitive within a broader exploit chain to tailor follow-on exploitation.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Internet Explorer legacy JScript (jscript.dll) vulnerability previously used in in-the-wild IE exploitation chains (mentioned for contrast with CVE-2020-1380).
An Internet Explorer vulnerability in handling the res:// URI scheme that was exploited to reveal the presence or absence of files on a victim system and help determine whether to deliver a second-stage exploit.
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.