CVE-2024-1939 is a high-severity type confusion vulnerability in the V8 JavaScript engine used by Google Chrome. In Chrome versions prior to 122.0.6261.94, a remote attacker could trigger heap corruption by causing the browser to process a crafted HTML page. The flaw arises from incorrect type handling within V8, which can lead to memory corruption during script execution or related page processing.
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 contains a working exploit for CVE-2024-1939, a type confusion vulnerability in the V8 JavaScript engine (as used in Chrome M122) related to improper handling of kWasmS128 in wasm-to-js conversion. The exploit is structured as follows: - `README.md` provides a detailed technical writeup explaining the vulnerability, exploitation strategy, and a sample JavaScript snippet for triggering the bug. - `main.html` is a minimal HTML file that loads `worker.js` as a Web Worker, which is used to stabilize memory addresses for reliable exploitation. - `worker.js` contains the main exploit logic. It allocates large ArrayBuffers to manipulate memory layout, then uses a crafted WebAssembly module to trigger the type confusion, resulting in a fake array object with arbitrary length. This enables out-of-bounds (OOB) read and write primitives. The script then constructs a ROP chain to perform syscalls (open/read/write) to exfiltrate the flag via stderr, demonstrating full code execution and sandbox escape. The exploit targets browsers or environments running the vulnerable V8 version with WebAssembly enabled. The only fingerprintable endpoint is the `worker.js` file, which is loaded as a Web Worker. No network or external endpoints are present. The exploit is operational and demonstrates a full chain from bug to code execution.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.