dbcve.org
ChromeWeb browser · Google

CVE-2024-9603

HIGH · 8.8 CVSS v3.1 Published 2024-10-08
Fix available
A fix is available. Upgrade to 129.0.6668.100 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
Type Confusion in V8 in Google Chrome prior to 129.0.6668.100 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 type confusion vulnerability in Google Chrome's V8 JavaScript engine allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This memory corruption flaw can be triggered when a user visits a malicious webpage, potentially leading to arbitrary code execution.

MitigationUpdate Google Chrome to version 129.0.6668.100 or later to patch the V8 type confusion vulnerability. Organizations should deploy browser updates through their patch management systems.

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

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 executable: On Windows, look for chrome.exe in Program Files or Program Files (x86). On macOS, check /Applications/Google Chrome.app. On Linux, run which google-chrome or find /usr -name 'google-chrome*'
    Affected if Chrome browser is present on the system
  2. Retrieve installed Chrome version
    Open chrome://version in the Chrome address bar and note the version number, or run 'google-chrome --version' from command line on Linux/macOS, or check registry on Windows at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe
    Affected if Unable to determine version indicates Chrome may not be properly installed
  3. Compare version against affected range
    Take the installed version number (e.g., 129.0.6668.90) and compare numerically to 129.0.6668.100 - the first three numeric segments (129.0.6668) must match, then check if the fourth segment is less than 100
    Affected if Installed version is lower than 129.0.6668.100 in the fourth numeric segment (e.g., .90, .70, .58)
  4. Check for automatic updates
    Visit chrome://settings/help to see if update status is displayed, or check if Chrome is configured for auto-updates via policy settings on managed devices
    Affected if Chrome shows update available or automatic updates are disabled

User is affected if Google Chrome is installed and the installed version number is less than 129.0.6668.100 when compared component-by-component.

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

Update Google Chrome to version 129.0.6668.100 or later to patch the V8 type confusion vulnerability. Organizations should deploy browser updates through their patch management systems.

Recommended fix High confidence

129.0.6668.100 or later (Chrome stable channel)

  1. Open Google Chrome browser
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. Chrome will automatically check for updates and download version 129.0.6668.100 or later
  6. Click 'Relaunch' to restart the browser and apply the update
  7. Verify the version by returning to 'About Google Chrome' and confirming the version number is 129.0.6668.100 or higher

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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