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 16 Sep 2024.
ChromeWeb browser · Google

CVE-2024-7971

CRITICAL · 9.6 CVSS v3.1 Published 2024-08-21
Fix available
A fix is available. Upgrade to 128.0.2739.42 / 128.0.6613.84 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Public exploit Remotely reachable No privileges Patch available

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
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)

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 type confusion vulnerability exists in Google Chrome's V8 JavaScript engine prior to version 128.0.6613.84. This flaw allows a remote attacker to exploit heap corruption by tricking users into visiting a specially crafted HTML page, potentially leading to arbitrary code execution.

MitigationUpdate Google Chrome to version 128.0.6613.84 or later. In enterprise environments, deploy browser updates via centralized endpoint management systems (e.g., Group Policy, SCCM, Intune) and verify compliance.

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
EdgeWeb browser
Affected:< 128.0.2739.42

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 Google Chrome version
    Navigate to chrome://settings/help in the browser address bar, or run 'google-chrome --version' from the command line
    Affected if The installed version is lower than 128.0.6613.84
  2. Check Microsoft Edge version
    Navigate to edge://settings/help in the browser address bar, or run 'msedge --version' from the command line
    Affected if The installed version is lower than 128.0.2739.42
  3. Confirm JavaScript is enabled
    In the browser, go to Settings > Privacy and security > Site Settings > JavaScript and verify the current configuration
    Affected if JavaScript is enabled in the browser settings, as the V8 JavaScript engine must be active for this vulnerability to be exploitable

You are affected if either Google Chrome below version 128.0.6613.84 or Microsoft Edge below version 128.0.2739.42 is installed and JavaScript is enabled in that browser.

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.2739.42 / 128.0.6613.84 or later
Fixed in 128.0.2739.42128.0.6613.84
Vendor patch www.microsoft.com →
Interim mitigation

Update Google Chrome to version 128.0.6613.84 or later. In enterprise environments, deploy browser updates via centralized endpoint management systems (e.g., Group Policy, SCCM, Intune) and verify compliance.

Recommended fix High confidence

Chrome 128.0.6613.84 or later / Edge 128.0.2739.42 or later

  1. Check the current browser version by navigating to chrome://settings/help (Chrome) or edge://settings/help (Edge)
  2. For Google Chrome: Navigate to the official Chrome download page or use the built-in update mechanism (Settings > Help > About Google Chrome) to update to version 128.0.6613.84 or later
  3. For Microsoft Edge: Navigate to the official Microsoft Edge download page or use the built-in update mechanism (Settings > About Microsoft Edge) to update to version 128.0.2739.42 or later
  4. Alternatively, use system-level package managers or enterprise deployment tools to push the updated browser versions across the organization
  5. Restart the browser after the update to ensure the new version is fully applied
  6. Verify the version update was successful by checking chrome://settings/help (Chrome) or edge://settings/help (Edge)
Caveat Browser security updates typically have minimal breaking changes but may include web compatibility adjustments; test critical web applications after updating

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

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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