Skip to content
Server Security Center
KEVhigh8.8

CVE-2023-7024: Google Chromium WebRTC Heap Buffer Overflow

Google Chromium WebRTC · listed in the CISA catalog of actively exploited vulnerabilities since 2024-01-02.

CVSS v3.1 (CVE record)
8.8
high
EPSS (exploit probability, 30 days)
6.7%
higher than 94% of all CVEs
Added to CISA KEV
2024-01-02
US federal due date 2024-01-23
Ubuntu priority
–

CVE-2023-7024 explained

CVE-2023-7024 is a heap buffer overflow in the WebRTC component of Google Chromium. A remote attacker could potentially exploit heap corruption through a crafted HTML page. CISA lists it as a known exploited vulnerability, so patching should be treated as urgent.

Impact

An attacker needs no privileges and can act over the network with low complexity. A user must open a crafted HTML page in the affected browser. Successful exploitation of the heap corruption could have a high impact on confidentiality, integrity and availability within the browser's security scope. Whether it has been used in ransomware campaigns is unknown.

Who is affected

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

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

Official description

Heap buffer overflow in WebRTC in Google Chrome prior to 120.0.6099.129 allowed a remote attacker to potentially 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
    • < 120.0.6099.129
    Fixed in
    • 120.0.6099.129

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 120.0.6099.129-1~deb12u1 or later from the standard archive.
  2. Close and restart all running Chromium instances so the patched code is loaded.
  3. Verify the installed chromium version on every system and user workstation.
  4. Follow the Debian security advisory for any further updates to chromium.

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-2023-7024

Is this vulnerability being exploited?
Yes. CISA added CVE-2023-7024 to its Known Exploited Vulnerabilities catalog on 2024-01-02, with a US federal due date of 2024-01-23. 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 must load a crafted HTML page in the vulnerable browser. No privileges are needed and the attack works over the network.
Is updating the package enough?
Updating chromium to 120.0.6099.129-1~deb12u1 installs the fix, but browsers that are already running keep the old code. Restart Chromium after the update.

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.