CVE-2022-4135
Memory Safety in Google Chrome ≤ 107.0.5304.121
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HSummary
CVE-2022-4135 is a critical-severity Out-of-bounds Write (CWE-787) vulnerability in Google Chrome. Its CVSS base score is 9.6 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 2% 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.
The vulnerability is a heap buffer overflow in the GPU component of Google Chrome versions prior to 107.0.5304.121, classified under CWE-787 as an out-of-bounds write. It resides in the browser's graphics processing path and carries a CVSS 3.1 score of 9.6 reflecting network attack vector, low complexity, and high impact across confidentiality, integrity, and availability when chained with a renderer compromise.
An attacker who has already gained control of the renderer process can deliver a crafted HTML page to trigger the flaw and attempt a sandbox escape, potentially gaining broader access to the underlying system.
Chrome release notes and the associated Gentoo advisory direct users to update immediately to version 107.0.5304.121 or later; the fix was shipped in the stable channel on 24 November 2022.
The EPSS score rose materially from a low baseline to a peak of 0.1960 on 2025-01-18 before receding, indicating that exploitation interest emerged well after disclosure and that the CVE merits renewed attention.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-7297
Vulnerability Data
Heap buffer overflow in GPU in Google Chrome prior to 107.0.5304.121 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
- CWE(s)
- KEV Date Added
- 28 November 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.
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-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
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 and acceptance can detect and prevent out-of-bounds write defects.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.
Change management can enforce review gates that catch unsafe memory operations before deployment.