Skip to content
Server Security Center
KEVcritical9.6

CVE-2024-4947: Google Chromium V8 Type Confusion

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

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

CVE-2024-4947 explained

CVE-2024-4947 is a type confusion flaw in the V8 JavaScript engine used by Chromium. In Google Chrome prior to 125.0.6422.60, a crafted HTML page could let a remote attacker execute arbitrary code inside the browser sandbox. It is listed in the CISA Known Exploited Vulnerabilities catalog, so it has been exploited in practice.

Impact

A remote attacker who gets a user to open a crafted HTML page can run arbitrary code inside the browser sandbox. No privileges are required and attack complexity is low, but user interaction is needed. The CVSS scope is changed, and confidentiality, integrity and availability impacts are all rated high. Any system where users browse untrusted content with an unpatched Chromium is exposed.

Who is affected

The facts list one affected release: Debian 12 (bookworm), source package chromium, in the standard archive. A fixed version is available there: 125.0.6422.60-1~deb12u1. No other Ubuntu or Debian releases are listed in the facts. Chromium builds older than 125.0.6422.60 are affected.

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

Official description

Type Confusion in V8 in Google Chrome prior to 125.0.6422.60 allowed a remote attacker to execute arbitrary code inside a sandbox 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
    • < 125.0.6422.60
    Fixed in
    • 125.0.6422.60

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 125.0.6422.60-1~deb12u1 or later.
  2. Close and restart all running Chromium instances so the patched code is loaded.
  3. Check that every managed workstation reports the updated Chromium version.
  4. Follow the Debian security advisory for Chromium and keep applying browser updates promptly.

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-843 Access of Resource Using Incompatible Type ('Type Confusion')

Questions about CVE-2024-4947

Is this vulnerability being exploited?
Yes. CISA added CVE-2024-4947 to its Known Exploited Vulnerabilities catalog on 2024-05-20. Whether it has been used in ransomware campaigns is listed as unknown.
Does installing the update protect users immediately?
Only after Chromium is restarted. Browser processes that are already running keep using the old code until they are closed and reopened.
Can an attacker exploit this without user action?
No. User interaction is required: the user must load a crafted HTML page. No privileges are needed, so any user browsing untrusted content with an unpatched browser is at risk.

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.