CVE-2024-4671criticalunder attackCWE-416

CVE-2024-4671: 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 8.3%
from disclosure to weapon
Published on NVDMay 9
CISA KEV+4d
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.

Affected
1 product (2 components)
Red Hat Enterprise Linux 6
workaround: Until updated packages are released for Fedora and EPEL, consider temporarily swapping to an alternative web browser such as Firefox or severely restricting activity to sites you know well and trust.
Action required by CISAfederal deadline: 2024-06-03

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

In short

A flaw in Google Chrome's visual rendering allows an attacker who already controls the browser's renderer process to escape the security sandbox through a specially crafted webpage, potentially gaining full system access.

Technical detail

Use-after-free vulnerability in the Visuals component allows a compromised renderer process to bypass sandbox isolation via crafted HTML. The attacker must first compromise the renderer, then trigger memory access after object deallocation to achieve arbitrary code execution with elevated privileges.

Summary generated and translated by AI from the official description.

The full analysis of this CVE is available in Portuguese →

Use after free in Visuals in Google Chrome prior to 124.0.6367.201 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