skip to content
Back to
Home Research Advisories CodeQL Wall of Fame Get Involved Events
September 27, 2023

GHSL-2023-137: Type confusion in Chrome - CVE-2023-3420

Man Yue Mo

Coordinated Disclosure Timeline


A type confusion caused by JSStackCheck can be exploited by an attacker to gain code execution in Chrome’s renderer.



Tested Version

version 114.0.5735.106


Type confusion in v8 caused by incorrect side effect modelling of JSStackCheck (GHSL-2023-137)

The JSStackCheck operator is marked with the kNoWrite property [1], which is used for operators that do not have side effects. This operator, however, can call into the Runtime::kStackGuard function [2], which can handle interrupts from other threads [3]. As can be seen from the definition of HandleInterrupts [4], it can call many different functions, some of which may have side effects [4]. In particular, the INSTALL_CODE [5] interrupt will install optimized JIT code, which can install the PrototypePropertyDependency and call EnsureHasInitialMap [6]. EnsureHasInitialMap takes the function argument, and checks if the initial_map field is already set, if not, then it will call SetInitialMap, which sets the prototype object of the function to the prototype of a map [7]. This then calls OptimizeAsPrototype [8], which can change the map of the prototype object. Combining this side effect with CheckMaps elimination in the LoadElimination optimization phase, a JSStackCheck can be used to change the map of an object after a CheckMaps is performed. Since JSStackCheck is inserted at the end of every loop iteration [9], this can be done by inserting a loop between a CheckMaps and a subsequent property access of an object whose map is checked before the loop (the CheckMaps after the loop is eliminated if the loop does not have any side effects other than the ones that come from JSStackCheck). By changing the object’s map in JSStackCheck after the CheckMaps is passed, a type confusion occurs.



Can be exploited to cause RCE in Chrome renderer



This issue was discovered and reported by GHSL team member @m-y-mo (Man Yue Mo).


You can contact the GHSL team at, please include a reference to GHSL-2023-137 in any communication regarding this issue.