dbcve.org
ChromeWeb browser · Google

CVE-2024-12382

HIGH · 8.8 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 131.0.6778.139 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
Use after free in Translate in Google Chrome prior to 131.0.6778.139 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

A use-after-free vulnerability exists in Google Chrome's Translate feature prior to version 131.0.6778.139. A remote attacker can exploit this by tricking users into visiting a crafted HTML page, leading to heap corruption and potential arbitrary code execution.

MitigationUpdate Google Chrome to version 131.0.6778.139 or later. Organizations should ensure automatic browser updates are enabled or deploy the update through their patch management infrastructure.

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

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 installed Chrome version
    Open Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on this page.
    Affected if The version shown is earlier than 131.0.6778.139 (for example, 131.0.6778.108 or any version below 131.0.6778.139).
  2. Verify Chrome auto-update status
    Navigate to chrome://settings/help in the address bar. Look for 'Update Google Chrome' button. If present, the browser is not updated. If it says 'Chrome is up to date', the update has been applied.
    Affected if The browser reports it is up to date with a version lower than 131.0.6778.139, or an update button is present indicating the vulnerable version is still running.
  3. Check if Translate feature is enabled
    Go to chrome://settings/languages. Look for the 'Offer to translate pages' option under Advanced languages settings.
    Affected if The Translate feature is enabled (toggle is on). The use-after-free vulnerability in CVE-2024-12382 only affects the Translate component when it is active.
  4. Confirm Chrome update mechanism status
    Navigate to chrome://settings/updates in the address bar. Check if 'Update Google Chrome' button appears or if updates are managed by system administrator.
    Affected if Updates are disabled or blocked, meaning the browser remains on a vulnerable version.

You are affected if Chrome is installed with a version lower than 131.0.6778.139 AND the Translate feature is enabled. If your version is 131.0.6778.139 or higher, you are not affected regardless of Translate settings.

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

Update Google Chrome to version 131.0.6778.139 or later. Organizations should ensure automatic browser updates are enabled or deploy the update through their patch management infrastructure.

Recommended fix High confidence

131.0.6778.139 or later

  1. Open Google Chrome browser
  2. Click on the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click on 'About Google Chrome'
  5. Chrome will automatically check for updates and display the current version
  6. If an update is available, click 'Update Google Chrome'
  7. Wait for the download and installation to complete
  8. Restart the browser to apply the update

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-12382 — 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-12382 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