dbcve.org
ChromeWeb browser · Google

CVE-2024-12693

HIGH · 8.8 CVSS v3.1 Published 2024-12-18
Fix available
A fix is available. Upgrade to 131.0.6778.204 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
Out of bounds memory access in V8 in Google Chrome prior to 131.0.6778.204 allowed a remote attacker to execute arbitrary code inside a sandbox 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 out-of-bounds memory access vulnerability in V8 (Google's JavaScript engine) in Google Chrome versions prior to 131.0.6778.204 allows a remote attacker to achieve arbitrary code execution through a malicious HTML page. The vulnerability exploits the sandboxed renderer process, which limits but does not eliminate the security impact.

MitigationUpdate Google Chrome to version 131.0.6778.204 or later to remediate this vulnerability. Organizations should deploy the update via their patch management systems and verify completion across all endpoints.

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.204

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 via command line
    Open terminal or command prompt and run: chrome --version (Windows) or /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version (Mac) or google-chrome --version (Linux)
    Affected if The version number displayed is lower than 131.0.6778.204
  2. Check Chrome version via browser UI
    Open Google Chrome, type chrome://version in the address bar, and press Enter. Locate the version string in the displayed information
    Affected if The Version field shows a number lower than 131.0.6778.204
  3. Check Chrome version via Windows Registry
    Open Registry Editor and navigate to HKEY_CURRENT_USER\Software\Google\Chrome\BLFeature or use reg query "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v Version
    Affected if The Version value is less than 131.0.6778.204
  4. Check Chrome version via PowerShell
    Run in PowerShell: (Get-Item 'C:\Program Files\Google\Chrome\Application\chrome.exe').VersionInfo.FileVersion or (Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome').DisplayVersion
    Affected if The returned version number is below 131.0.6778.204

If the installed Google Chrome version is any build lower than 131.0.6778.204, the environment is affected by this vulnerability.

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.204 or later
Fixed in 131.0.6778.204
Interim mitigation

Update Google Chrome to version 131.0.6778.204 or later to remediate this vulnerability. Organizations should deploy the update via their patch management systems and verify completion across all endpoints.

Recommended fix High confidence

Chrome 131.0.6778.204 or later

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Chrome will automatically check for updates; if version 131.0.6778.204 or later is available, click 'Update Google Chrome'
  3. Restart the browser to complete the installation
  4. Verify the update by returning to Settings > Help > About Google Chrome and confirming the version is 131.0.6778.204 or later
Caveat Security patch updates typically have minimal breaking changes; however, some extensions or web apps may require adjustments for compatibility with the updated V8 engine

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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