Skip to content
Server Security Center
KEVcritical9.6

CVE-2024-7971: Google Chromium V8 Type Confusion

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

CVSS v3.1 (CVE record)
9.6
critical
EPSS (exploit probability, 30 days)
21%
higher than 97.6% of all CVEs
Added to CISA KEV
2024-08-26
US federal due date 2024-09-16
Ubuntu priority
–

CVE-2024-7971 explained

CVE-2024-7971 is a type confusion flaw in the V8 JavaScript engine used by Google Chrome and Chromium. A remote attacker can cause heap corruption by getting a user to open a crafted HTML page. CISA lists it as known to be exploited, so affected browsers should be updated promptly.

Impact

An attacker needs no privileges and no local access. The user only has to open a malicious web page. Successful exploitation can cause heap corruption with high impact on confidentiality, integrity and availability. The scope is changed, so effects can reach beyond the vulnerable component. Attack complexity is low. CISA lists the flaw in its Known Exploited Vulnerabilities catalog, but whether it has been used in ransomware is unknown.

Who is affected

The facts list one affected release: Debian 12 (bookworm), source package chromium, from the standard archive. A fixed version, 128.0.6613.84-1~deb12u1, is published for this release. No other Debian or Ubuntu releases are listed in the facts.

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 128.0.6613.84 allowed a remote attacker to exploit heap corruption 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
    • < 128.0.6613.84
    Fixed in
    • 128.0.6613.84

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. On Debian 12 (bookworm), update the chromium package to 128.0.6613.84-1~deb12u1 or later.
  2. Close and restart all running Chromium instances so the patched code is loaded.
  3. Check that every user workstation and kiosk running Chromium has received the update.
  4. Follow the Debian security advisory for any later Chromium 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-843 Type confusion

Questions about CVE-2024-7971

Is this vulnerability exploited in the wild?
CISA added CVE-2024-7971 to its Known Exploited Vulnerabilities catalog on 2024-08-26, with a US federal due date of 2024-09-16. Known ransomware use is listed as unknown.
Does a user need to do anything for an attack to work?
Yes. User interaction is required. The user has to open a crafted HTML page in a vulnerable browser. No privileges are needed.
Is the update enough on its own?
Install 128.0.6613.84-1~deb12u1 or later, then restart Chromium. Browser processes that are already running keep using the old code until they are restarted.

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.