Loading vulnerability…
CVE-2022-4262 is a high-severity type confusion vulnerability in the V8 JavaScript engine in Google Chrome prior to 108.0.5359.94. The flaw resides in the V8 parser’s handling of class static initialization blocks, where use of this inside a static block could incorrectly propagate through the ExpressionScope chain and mark an enclosing function as using this. Analysis of the fix indicates the issue was addressed by introducing a FunctionParsingScope while parsing class static blocks, preventing incorrect scope propagation. This parser error could lead to inconsistent bytecode generation for the same function, particularly when V8 bytecode flushing caused bytecode to be regenerated from stored parsing results. Researchers showed that stale assumptions about context layout in nested functions could then be abused to access unintended contexts, including NativeContext-resident objects, and to swap internal Map objects in a way that produced type confusion. The resulting condition enabled powerful memory corruption primitives 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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a proof-of-concept exploit for CVE-2022-4262, a type confusion vulnerability in the V8 JavaScript engine used by Chromium. The main exploit logic is implemented in 'exploit.js', which demonstrates how to manipulate V8's feedback vector and object maps to achieve arbitrary memory read and write capabilities. The exploit is designed to be run in the d8 JavaScript shell, requiring a specific V8 commit and build configuration. Supporting files include 'ic.js' (demonstrating feedback vector manipulation), 'test.js' (testing feedback vector type confusion), and a patch file 'dbg.patch' for enhanced debugging. The repository also includes before/after GC state dumps for analysis. The exploit is a proof-of-concept and does not include a weaponized payload, but it provides the necessary primitives for further exploitation. The primary attack vector is via a browser context, targeting V8 in Chromium-based browsers.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A V8 parser/module vulnerability in Chrome discussed through patch diff and exploit development research; the content states Chrome fixed a V8 vulnerability that was being exploited in the wild, and the researchers developed a PoC and exploitation path involving bytecode inconsistency and type confusion.
A Chrome V8 engine vulnerability in the Parser module involving incorrect ExpressionScope handling for class static blocks, leading to inconsistent bytecode generation and enabling type confusion exploitation primitives.
Chrome type confusion vulnerability used as part of an exploit chain against Samsung Internet Browser (Chromium 102).
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.