Skip to content
Server Security Center
KEVcritical9.6

CVE-2024-4671: Google Chromium Visuals Use-After-Free

Google Chromium · listed in the CISA catalog of actively exploited vulnerabilities since 2024-05-13.

CVSS v3.1 (CVE record)
9.6
critical
EPSS (exploit probability, 30 days)
8.3%
higher than 95% of all CVEs
Added to CISA KEV
2024-05-13
US federal due date 2024-06-03
Ubuntu priority
–

CVE-2024-4671 explained

CVE-2024-4671 is a use-after-free flaw in the Visuals component of Google Chromium before 124.0.6367.201. A remote attacker who has already compromised the renderer process could use a crafted HTML page to potentially escape the browser sandbox. CISA lists it as a known exploited vulnerability, so patching should be a priority.

Impact

An attacker who has already compromised the renderer process could break out of the Chromium sandbox. The attack works over the network, needs no privileges, and requires the user to open a crafted HTML page. Because the scope is changed, a successful attack can reach beyond the browser process. It can affect confidentiality, integrity and availability of the system at a high level.

Who is affected

The facts list one affected release. On Debian 12 (bookworm), the chromium source package is affected. A fix is available in the standard archive as version 124.0.6367.201-1~deb12u1. The facts include no Ubuntu releases and no other Debian releases, so their status is not covered here.

Written with AI from the data on this page and checked against it automatically.

Official description

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)

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • Google Chrome
    Affected
    • < 124.0.6367.201
    Fixed in
    • 124.0.6367.201

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Update the chromium package on Debian 12 (bookworm) to 124.0.6367.201-1~deb12u1 or later.
  2. Close and restart all running Chromium instances so the patched code is loaded.
  3. Check that every workstation and server with Chromium installed runs the fixed version.
  4. Follow the Debian security advisory for Chromium for any later updates.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace chromium with the source package from the table above.

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="chromium"'

2. Compare each installed version with the fixed version for your release from the table

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="chromium"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-416 Use After Free

Questions about CVE-2024-4671

Is this vulnerability being exploited?
Yes. CISA added CVE-2024-4671 to its Known Exploited Vulnerabilities catalog on 2024-05-13. The due date for US federal agencies was 2024-06-03. Whether it has been used in ransomware campaigns is listed as unknown.
Do I need to reboot after updating?
A full reboot is not required. Running Chromium processes keep using the old code until they are closed. Restart the browser after the update so the fix takes effect.
Can an attacker exploit this flaw on its own?
According to the description, the attacker must already have compromised the renderer process. The user must also open a crafted HTML page. The flaw is then used to escape the sandbox.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.