Skip to content
Server Security Center
KEVhigh8.8

CVE-2024-4761: Google Chromium V8 Out-of-Bounds Memory Write

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

CVSS v3.1 (CVE record)
8.8
high
EPSS (exploit probability, 30 days)
11%
higher than 96% of all CVEs
Added to CISA KEV
2024-05-16
US federal due date 2024-06-06
Ubuntu priority
–

CVE-2024-4761 explained

CVE-2024-4761 is an out-of-bounds write in V8, the JavaScript engine in Google Chromium. A crafted HTML page can make the browser write memory outside its intended bounds. The flaw is listed in the CISA Known Exploited Vulnerabilities catalog, so it has been exploited in the wild, and affected browsers should be updated promptly.

Impact

A remote attacker who gets a user to open a crafted HTML page can trigger an out-of-bounds memory write in V8. No privileges are needed, but user interaction is required. According to the CVSS rating, a successful attack can have high impact on confidentiality, integrity and availability within the browser's context. Any system where users browse untrusted web content with an affected Chromium build is exposed.

Who is affected

The facts cover the chromium source package on Debian 12 (bookworm), a supported release. A fixed version, 124.0.6367.207-1~deb12u1, is available in the standard archive. The upstream description states that Google Chrome versions before 124.0.6367.207 are affected. No other releases or packages are listed in the facts.

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

Official description

Out of bounds write in V8 in Google Chrome prior to 124.0.6367.207 allowed a remote attacker to perform an out of bounds memory write 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.207
    Fixed in
    • 124.0.6367.207

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. Identify Debian 12 (bookworm) systems with the chromium package installed.
  2. Upgrade chromium to 124.0.6367.207-1~deb12u1 or later from the standard archive.
  3. Close and restart all running Chromium instances so the patched code is loaded.
  4. Verify the installed package version on each system after the upgrade.
  5. Because the flaw is known to be exploited, prioritize this update on systems used for general web browsing.

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-787 Out-of-bounds Write

Questions about CVE-2024-4761

Is CVE-2024-4761 being actively exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-05-16, with a US federal due date of 2024-06-06. Whether it has been used in ransomware campaigns is unknown.
Which Debian package version fixes it?
On Debian 12 (bookworm), the chromium package is fixed in version 124.0.6367.207-1~deb12u1, available from the standard archive.
Do I need to restart anything after updating?
Yes. Running Chromium processes keep using the old code until they are closed. Restart the browser after the package upgrade so the fix takes effect.

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.