CVE-2022-4135criticalunder attackCWE-787

CVE-2022-4135: critical vulnerability in Google Chrome

Published · Updated

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

70Vexday Risk Score

Prioritize patching. It under exploitation confirmed by CISA.

ssvc Actcvss 9.6epss 32%
from disclosure to weapon
Published on NVDNov 25
CISA KEV+3d
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Not affected
1 product — because the vulnerable code is not present in the product
red_hat_products
Action required by CISAfederal deadline: 2022-12-19

Apply updates per vendor instructions.

In short

A memory overflow flaw in Chrome's GPU component allowed attackers who compromised the browser's renderer to escape the sandbox and gain full system access. This is critical because it enables attackers to break out of Chrome's security isolation.

Technical detail

Heap buffer overflow in the GPU command processing pipeline (CWE-787) in Chrome versions prior to 107.0.5304.121. Requires prior renderer process compromise as precondition; triggered via crafted HTML page. Impacts confidentiality, integrity, and availability through sandbox escape.

Summary generated and translated by AI from the official description.

The full analysis of this CVE is available in Portuguese →

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)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Affected products
Google · Chrome