Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2023-2935 is a high-severity Type Confusion (CWE-843) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-2935 is a type confusion vulnerability in the V8 JavaScript engine within Google Chrome versions prior to 114.0.5735.90. The flaw, assigned CWE-843, permits heap corruption when a specially crafted HTML page is processed, carrying a CVSS 3.1 base score of 8.8 and a Chromium security severity rating of High.
A remote attacker can trigger the issue by convincing a user to visit a malicious web page, after which successful exploitation may allow arbitrary code execution with the privileges of the Chrome process. The attack requires no authentication and can be delivered over the network with only user interaction via the browser.
Chrome release notes and downstream advisories such as Gentoo GLSA-202311-11 and GLSA-202401-34 direct users to apply the stable-channel update that resolves the defect in V8. The referenced proof-of-concept on Packet Storm demonstrates the type-confusion primitive but does not indicate widespread in-the-wild exploitation; EPSS scores remained low, peaking near 0.10 before receding.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-34381
Vulnerability Data
Type Confusion in V8 in Google Chrome prior to 114.0.5735.90 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.5.2V3.2.3V15.3.5
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional weaknesses.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect type-confusion vulnerabilities through fuzzing and static analysis.
Secure SDLC mandates type-safe design and review that can catch type-confusion flaws.
Application security requirements can specify strong typing and interface contracts that reduce type confusion.
Secure architecture principles promote type-safe languages and memory-safety mechanisms that mitigate type confusion.
Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.