Loading vulnerability…
CVE-2019-0752 is a remote code execution vulnerability in the Internet Explorer scripting engine caused by improper handling of objects in memory. The flaw is described as a scripting engine memory corruption issue in which crafted web content can trigger unsafe memory operations while Internet Explorer processes scriptable objects. Successful exploitation can corrupt process memory and allow attacker-controlled code to execute in the context of the browser process.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a proof-of-concept (PoC) exploit for CVE-2019-0752, a write-what-where vulnerability in Internet Explorer 11's scripting engine on Windows 10 x64 (32-bit IE). The exploit is implemented in a single HTML file (exploit.html) that combines JavaScript and VBScript to manipulate DOM elements and memory structures. The exploit achieves arbitrary read/write in memory, locates KERNEL32.dll, resolves the address of WinExec, and hijacks a vtable to execute arbitrary commands. The payload is not hardcoded and does not use external scripts like PowerShell, making it stealthier. The only fingerprintable endpoint is the string '\..\splwow64', used internally in the exploit's memory manipulation. The README provides context and references the original ZDI blog post. The exploit is a functional PoC and demonstrates code execution, but does not include a weaponized or easily customizable payload.
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.
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.