Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2022-1364 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 4% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities 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-2022-1364 is a type confusion vulnerability (CWE-843) in the V8 Turbofan component of Google Chrome versions prior to 100.0.4896.127. The flaw resides in the JavaScript engine's optimization pipeline and can be triggered by a specially crafted HTML page, resulting in heap corruption.
A remote attacker can exploit the issue by convincing a user to visit a malicious web page. Successful exploitation grants the attacker the ability to corrupt memory and achieve high-impact effects on confidentiality, integrity, and availability without requiring authentication.
Chrome release notes and the associated Gentoo advisory direct users to apply the stable-channel update that resolves the issue in version 100.0.4896.127 and later.
The EPSS score rose materially from lower values to a peak of 0.3373 on 2024-12-17 before receding to the current 0.1751, indicating renewed exploitation interest well after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-24685
Vulnerability Data
Type confusion in V8 Turbofan in Google Chrome prior to 100.0.4896.127 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
- CWE(s)
- KEV Date Added
- 15 April 2022
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.