Loading vulnerability…
CVE-2023-3079 is a high-severity type confusion vulnerability in the V8 JavaScript engine used by Google Chrome prior to 114.0.5735.110. The flaw occurs in inline cache handling for property writes involving JSStrictArgumentsObject. Specifically, the StoreFastElementIC_GrowNoTransitionHandleCOW path can grow an elements backing store without performing the required transition from PACKED_ELEMENTS to HOLEY_ELEMENTS. This leaves the object in an inconsistent state where holes exist but the map still indicates packed elements. As a result, V8 can expose the internal sentinel value known as The Hole to JavaScript. The leaked value can then be used to trigger a JIT type inference error in Turbofan, causing bounds checks to be incorrectly optimized away and enabling out-of-bounds array access. From that primitive, an attacker can derive address-of and arbitrary read/write capabilities within the renderer process heap, leading to heap corruption and a path toward renderer code execution via a crafted HTML page.
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 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.
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.
6 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.
A Chrome renderer remote code execution vulnerability in the V8 JavaScript engine caused by type confusion in inline cache handling for JSStrictArgumentsObject property writes, enabling leakage of 'The Hole' value and subsequent out-of-bounds access for exploitation.
Another in-the-wild V8 vulnerability referenced as an example of achieving sandbox bypass and code execution, related to the discussed V8 sandbox escape technique.
Known vulnerability in Chromium’s V8 engine referenced as part of the actor’s CVE research.
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.