CVE-2022-3075criticalunder attack

CVE-2022-3075: critical vulnerability in Google Chrome

Published · Updated

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

58Vexday Risk Score

Prioritize patching. It under exploitation confirmed by CISA.

ssvc Actcvss 9.6epss 5.8%
from disclosure to weapon
Published on NVDSep 26
CISA KEVSep 8
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-09-29

Apply updates per vendor instructions.

In short

A flaw in Google Chrome's Mojo system allowed attackers who compromised the browser's renderer to escape the security sandbox and access the full system. This is dangerous because the sandbox normally blocks malicious code from doing serious damage.

Technical detail

Insufficient input validation in Mojo before Chrome 105.0.5195.102 enabled sandbox escape when an attacker with renderer process compromise could craft a malicious HTML page to trigger the vulnerability. Attack requires prior renderer compromise; impact is critical as it breaks the isolation boundary protecting the system from browser-based exploits.

Summary generated and translated by AI from the official description.

The full analysis of this CVE is available in Portuguese →

Insufficient data validation in Mojo in Google Chrome prior to 105.0.5195.102 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Affected products
Google · Chrome