CVE-2023-6702 is a high-severity type confusion vulnerability in the V8 JavaScript engine used by Google Chrome. In Google Chrome versions prior to 120.0.6099.109, improper handling of object types in V8 could be triggered by a crafted HTML page, leading to heap corruption. This memory safety flaw may enable an attacker to corrupt process memory during script execution within the browser context.
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 fully functional exploit for CVE-2023-6702, a type confusion vulnerability in the V8 JavaScript engine used by Google Chrome. The exploit targets Chrome versions prior to 120.0.6099.109 and achieves remote code execution in the renderer process. The repository includes several files: - README.md: Provides a detailed technical write-up of the vulnerability, exploitation strategy, and references to related research and patches. - exploit.html: The main exploit file, containing JavaScript code that leverages the vulnerability to gain arbitrary read/write primitives, leak addresses, and execute a ROP chain to run arbitrary system commands (e.g., launching xcalc via /bin/bash). - fake_frame.js: Contains helper code for constructing fake async stack frames, used as part of the exploitation process. - index.html: Orchestrates the attack by creating multiple iframes that load the exploit, simulating a real-world attack scenario where a user visits a malicious web page. - poc.js: A minimal proof-of-concept script demonstrating the initial trigger of the vulnerability. The exploit is operational and demonstrates a full chain from vulnerability trigger to code execution. The attack vector is via the browser, requiring the victim to visit a malicious web page. The exploit is highly technical, leveraging advanced JavaScript and V8 internals, and is suitable for researchers or red teamers. The payload is customizable but, as provided, launches a system command on the target. The repository does not use any exploit frameworks and is a standalone exploit.
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 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.