Loading vulnerability…
A vulnerability in the V8 JavaScript engine in Google Chrome prior to version 72.0.3626.96 arises from incorrect handling of deferred code, which can be triggered by a remote attacker through a crafted HTML page. This flaw can lead to heap corruption, potentially allowing for arbitrary code execution within the context of the browser.
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 proof-of-concept (PoC) exploit for CVE-2019-5784, a type confusion vulnerability in the V8 JavaScript engine used by Google Chrome. The repository contains three files: a README.md describing the PoC, a main.js file with the actual exploit code, and an html.html file that appears to be a demonstration wrapper for the exploit but is marked as unnecessary by the author. The main.js file implements a recursive function that manipulates function arguments and attempts to create large typed arrays, aiming to trigger the type confusion vulnerability in V8. The exploit is designed to be run in a vulnerable version of Chrome or any environment using the affected V8 engine. No network endpoints, IP addresses, or other fingerprintable targets are present in the code. The PoC does not provide a weaponized payload or post-exploitation capabilities; it is intended to demonstrate the vulnerability trigger for research or testing purposes.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.