Loading vulnerability…
CVE-2019-5782 is a remote code execution vulnerability in the V8 JavaScript engine in Google Chrome prior to version 72.0.3626.81. The vulnerability arises from incorrect optimization assumptions in V8, which can be exploited by a remote attacker through a crafted HTML page to execute arbitrary code within the Chrome sandbox. This vulnerability was actively exploited in the wild as part of Operation Earth Kitsune, where it was used as an initial infection vector to deliver custom espionage malware such as SLUB, dneSpy, and agfSpy.
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.
This repository is a browser exploit targeting Google Chrome 71.0.3578.98 on Windows 10, specifically exploiting CVE-2019-5782 and CVE-2019-13768. The exploit is implemented as a local web server (server.py) that serves a crafted HTML/JavaScript payload (index.html and associated JS files) to the target browser. The exploit leverages a use-after-free vulnerability in the FileWriter Mojo interface, using advanced heap spraying and ROP techniques to achieve arbitrary code execution in the Chrome renderer process. The payload is customizable shellcode (default: launches calc.exe), provided in shellcode.asm. The exploit is operational and reliable on Windows 10 1909+ with the specified Chrome version. The repository includes all necessary Mojo bindings and interface files for the exploit to function. The main attack vector is browser-based, requiring the victim to visit the attacker's server. The structure is modular, with clear separation between the exploit logic, payload, and supporting interface definitions.
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.
1 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.