CVE-2022-3723
Memory Safety in Google Chrome ≤ 107.0.5304.87
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2022-3723 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 6% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vulnerability is a type confusion flaw, tracked as CWE-843, in the V8 JavaScript engine of Google Chrome versions prior to 107.0.5304.87. It can result in heap corruption when processing specially crafted input and carries a CVSS 3.1 base score of 8.8.
A remote attacker can exploit the issue by serving a malicious HTML page to a victim who visits it in an affected browser. Successful exploitation may allow the attacker to corrupt memory and achieve impacts consistent with the high severity rating, including potential code execution within the renderer process.
Chrome release notes and distribution advisories such as Gentoo GLSA-202305-10 direct users to upgrade immediately to version 107.0.5304.87 or later; the corresponding Chromium bug tracker entry confirms the fix was included in the October 2022 stable channel update.
The EPSS probability for CVE-2022-3723 rose from low values at disclosure to a peak of 0.0177 on 2024-06-29 before receding to the current 0.0051, indicating a notable increase in exploitation interest more than eighteen months after publication.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-43079
Vulnerability Data
Type confusion in V8 in Google Chrome prior to 107.0.5304.87 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
- CWE(s)
- KEV Date Added
- 28 October 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.