dbcve.org
ChromeWeb browser · Google

CVE-2024-12694

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
Use after free in Compositing in Google Chrome prior to 131.0.6778.204 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

Use-after-free vulnerability in Chrome's compositing component allows a remote attacker to exploit heap corruption via a malicious HTML page. The flaw occurs when the browser continues using memory after it has been freed, potentially enabling arbitrary code execution.

MitigationUpdate Google Chrome to version 131.0.6778.204 or later. Organizations should deploy browser patches through their patch management systems and verify completion across 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. Verify Google Chrome is installed
    Check for Chrome installation: On Windows, look for Chrome in Program Files or via 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome"' or check for chrome.exe in typical paths. On macOS, check /Applications/Google Chrome.app. On Linux, check for google-chrome in package manager or /usr/bin/google-chrome.
    Affected if Chrome is installed on the system
  2. Determine installed Chrome version
    Open Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' from command line on macOS/Linux. On Windows, run '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' or check the version property of chrome.exe.
    Affected if Unable to determine version (Chrome may be corrupted or restricted)
  3. Compare version against affected range
    Parse the installed version number and compare it to 131.0.6778.204. Any version less than 131.0.6778.204 is affected (e.g., 131.0.6778.203, 130.x.x.x, 129.x.x.x, etc.).
    Affected if Installed version is less than 131.0.6778.204
  4. Assess user exposure to malicious content
    Determine if users in the environment browse untrusted websites or open untrusted HTML files, as the exploit requires a user to visit a malicious page hosting the exploit.
    Affected if Users routinely access untrusted websites or open HTML attachments from unknown sources

The environment is affected if Google Chrome is installed with a version lower than 131.0.6778.204 and users could potentially open a malicious HTML page.

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. Organizations should deploy browser patches through their patch management systems and verify completion across endpoints.

Recommended fix High confidence

Chrome 131.0.6778.204 or later

  1. Open Google Chrome browser
  2. Click the menu icon (three dots) in the top-right corner
  3. Select 'Help' then 'About Google Chrome'
  4. Chrome will check for updates and automatically download the latest version
  5. Click 'Relaunch' to restart Chrome and apply the update
  6. Verify the version is 131.0.6778.204 or later by returning to Help > About Google Chrome
Caveat Chrome updates typically have minimal breaking changes; however, some older extensions or web apps may experience compatibility issues with the newest release

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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