dbcve.org
ChromeWeb browser · Google

CVE-2024-7972

HIGH · 8.8 CVSS v3.1 Published 2024-08-21
Fix available
A fix is available. Upgrade to 128.0.6613.84 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Inappropriate implementation in V8 in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: Medium)

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

A vulnerability in the V8 JavaScript engine in Google Chrome versions prior to 128.0.6613.84 allows a remote attacker to perform out-of-bounds memory access via a specially crafted HTML page, potentially leading to memory corruption that could be exploited for code execution or information disclosure.

MitigationUpdate Google Chrome to version 128.0.6613.84 or later. This is a browser-side vulnerability with no server-side component.

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:< 128.0.6613.84

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
    On Windows, look for Google Chrome in Program Files or the Start Menu. On macOS, check /Applications for Google Chrome. On Linux, run 'which google-chrome' or check common installation directories.
    Affected if Google Chrome is not installed on the system - the vulnerability only affects Google Chrome, not Chromium or other browsers based on different engines.
  2. Find the installed Chrome version
    Open Google Chrome and navigate to chrome://settings/help, or type chrome://version in the address bar. The version number is displayed at the top of the settings page or in the first line of the version information.
    Affected if The version cannot be determined - you must know the exact version to assess exposure.
  3. Compare your version against the affected range
    Locate the version number from step 2 (format is typically X.X.X.X such as 128.0.6613.84). Compare the first three numeric groups to 128.0.6613. Any version below 128.0.6613.84 is affected; version 128.0.6613.84 and later are patched.
    Affected if Your installed version is less than 128.0.6613.84 - this means the V8 out-of-bounds memory access vulnerability is present in your Chrome installation.
  4. Verify V8 JavaScript engine is enabled
    The V8 engine is built into Chrome and cannot be disabled by users. To confirm it is active, open chrome://version and look for V8 version information in the command line, or visit any website and open Developer Tools (F12) to see the JavaScript engine reported in the console.
    Affected if This step confirms the vulnerable component is present - V8 is always enabled in Chrome, so this validates the attack surface exists.

You are affected if Google Chrome is installed and the version is less than 128.0.6613.84, since the V8 engine is always enabled and cannot be disabled.

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 128.0.6613.84 or later
Fixed in 128.0.6613.84
Interim mitigation

Update Google Chrome to version 128.0.6613.84 or later. This is a browser-side vulnerability with no server-side component.

Recommended fix High confidence

Chrome 128.0.6613.84 or later (stable channel)

  1. Open Google Chrome browser
  2. Click the three-dot menu (⋮) in the top-right corner
  3. Select 'Help' > 'About Google Chrome'
  4. The browser will check for updates and automatically download the latest version
  5. Click 'Relaunch' to apply the update, or close and reopen Chrome manually
  6. Verify the version is 128.0.6613.84 or later by returning to Help > About Google Chrome

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7972 — 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-2024-7972 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