dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 23 Jan 2024.
ChromeWeb browser · Google

CVE-2023-7024

HIGH · 8.8 CVSS v3.1 Published 2023-12-21
Fix available
A fix is available. Upgrade to 120.0.6099.129 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Public exploit Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Heap buffer overflow vulnerability in Google Chrome's WebRTC component allows remote attackers to exploit heap corruption via malicious HTML pages. The flaw exists in versions prior to 120.0.6099.129 and enables potential code execution through crafted WebRTC session content.

MitigationUpdate Google Chrome to version 120.0.6099.129 or later to patch the vulnerability. Organizations should deploy the update across all endpoints and verify successful installation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 120.0.6099.129
Debian LinuxOperating system
Affected:= 11.0= 12.0
FedoraOperating system
Affected:= 38= 39

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Google Chrome is installed
    Open terminal and run: google-chrome --version OR chrome --version OR look for Chrome in /usr/bin/google-chrome
    Affected if Chrome is not found in common installation paths, the vulnerability does not apply (but also means Chrome may not be installed)
  2. Determine installed Chrome version
    Run: google-chrome --version in terminal, or navigate to chrome://settings/help in the browser address bar
    Affected if Version number displayed is lower than 120.0.6099.129
  3. Check Chromium package version on Debian
    Run: dpkg -l | grep chromium or apt show chromium, or check installed version with: apt-cache policy chromium
    Affected if Installed version matches Debian 11.0 or 12.0 and is not patched to the fixed version
  4. Check Chromium package version on Fedora
    Run: rpm -qa | grep chromium or dnf list installed chromium
    Affected if Installed version matches Fedora 38 or 39 and is not patched to the fixed version

A user is affected if Google Chrome or its Chromium package version is below 120.0.6099.129, as versions prior to this contain the vulnerable WebRTC component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 120.0.6099.129 or later
Fixed in 120.0.6099.129
Interim mitigation

Update Google Chrome to version 120.0.6099.129 or later to patch the vulnerability. Organizations should deploy the update across all endpoints and verify successful installation.

Recommended fix High confidence

Chrome 120.0.6099.129 or later (or latest available Chromium package from your distribution)

  1. For Google Chrome desktop users: Navigate to Settings > Help > About Google Chrome and verify the version is 120.0.6099.129 or later. If not, the browser will automatically check for updates and prompt you to restart.
  2. Alternatively, download the latest stable Chrome version from the official Google Chrome website.
  3. For Debian Linux systems (versions 11.0 and 12.0): Run 'sudo apt-get update' followed by 'sudo apt-get upgrade' or 'sudo apt-get dist-upgrade' to install the latest Chromium security updates.
  4. For Fedora Linux systems (versions 38 and 39): Run 'sudo dnf update' or 'sudo dnf upgrade' to apply the latest security patches for Chromium.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-7024 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-7024 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data