Loading vulnerability…
A type confusion vulnerability exists in the V8 JavaScript engine in Google Chrome prior to version 83.0.4103.61. The flaw allows a remote attacker to trigger heap corruption by enticing a user to visit a specially crafted HTML page, exploiting improper handling of object types within V8.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a working exploit for CVE-2020-6468, a vulnerability in the V8 JavaScript engine used by Google Chrome. The exploit is provided in two forms: 'exploit_chrome.html' (for use in the Chrome browser) and 'exploit_d8.js' (for use in the d8 JavaScript shell). Both exploits leverage a bug in argument length optimization to achieve out-of-bounds (OOB) read/write, which is then used to gain arbitrary read/write primitives in the V8 heap. The exploit proceeds to inject shellcode (provided as a byte array) into a RWX memory region (such as a WebAssembly instance or a corrupted ArrayBuffer) and triggers its execution, resulting in arbitrary code execution. The repository is structured with a README describing the exploit, and two main code files: the HTML/JavaScript exploit for Chrome and the JavaScript exploit for d8. No external network endpoints or domains are hardcoded; the attack is local to the browser or JavaScript engine. The exploit is operational and demonstrates full code execution capability.
This repository is a proof-of-concept (PoC) exploit for CVE-2020-6468, a vulnerability in the Chromium browser (version 81.0.4044.92) that allows for arbitrary code execution in the renderer process. The exploit is implemented as a single HTML file ('cve-2020-6468-no-sandbox.html') containing JavaScript code that abuses a type confusion or out-of-bounds access to achieve arbitrary read/write primitives. It then leverages WebAssembly to obtain a RWX memory page, injects shellcode, and executes it via a WebAssembly function. The exploit requires Chromium to be run with the '--no-sandbox' flag, making it suitable for research or demonstration purposes but not directly weaponized for real-world attacks. The README provides environment setup instructions and references the official Chromium bug tracker. No network endpoints or external services are targeted; the exploit is self-contained and operates entirely within the browser context.
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.