Type Confusion in Google Chrome V8
CVE-2023-3079 is a type confusion vulnerability in the V8 JavaScript engine in Google Chrome prior to 114.0.5735.110. According to the provided content, the flaw allowed a remote attacker to potentially trigger heap corruption by convincing a target to process a crafted HTML page. The vulnerable condition arises from incorrect type handling within V8, which can cause the engine to treat an object as an incompatible type during JavaScript execution, leading to memory corruption on the heap.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept exploit for CVE-2023-3079, a vulnerability in the V8 JavaScript engine used by Google Chrome and other Chromium-based browsers. The exploit is implemented in JavaScript and is designed to be run in the d8 shell (the V8 standalone shell) built from a specific vulnerable commit. The repository includes two main JavaScript files: 'exploit.js' (the main exploit with comments and usage instructions) and 'exploit-commentless.js' (a version with fewer comments). There is also a patch file to fix a build error unrelated to the vulnerability itself. The exploit achieves arbitrary memory read and write primitives by abusing a bug in the handling of the arguments object, which can be leveraged for further exploitation such as remote code execution. The README provides references to writeups, resources, and relevant V8 source code and patches. No network endpoints or remote services are targeted; the exploit is local and must be run in a controlled environment with a vulnerable V8 build.
Affected products & vendors
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.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A type confusion vulnerability in V8 JavaScript engine in Google Chrome, exploited by Predator spyware.
Known vulnerability in Chromium’s V8 engine referenced as part of the actor’s CVE research.
The version that knows your environment.
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.