dbcve.org
ChromeWeb browser · Google

CVE-2024-9956

HIGH · 7.8 CVSS v3.1 Published 2024-10-15
Fix available
A fix is available. Upgrade to 130.0.6723.58 or later.
See remediation →
81/100
Remediation priority · High
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
Inappropriate implementation in WebAuthentication in Google Chrome on Android prior to 130.0.6723.58 allowed a local attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Medium)

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 vulnerability in Google Chrome's WebAuthentication (WebAuthn) implementation on Android prior to version 130.0.6723.58 allows a local attacker with the ability to deliver a crafted HTML page to perform privilege escalation. The inappropriate implementation in the WebAuthn API permits bypassing intended security boundaries.

MitigationUpdate Google Chrome for Android to version 130.0.6723.58 or later. In enterprise environments, deploy the update via mobile device management (MDM) policies to ensure all managed devices receive the patch.

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

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 Chrome for Android version
    Open Chrome, tap the three-dot menu, go to Settings > About Chrome. The version number is displayed at the top.
    Affected if The version shown is less than 130.0.6723.58
  2. Verify Chrome version in Play Store
    Open Google Play Store, search for Chrome, tap on Chrome, and check the version listed under 'Additional information'.
    Affected if The Play Store shows a version lower than 130.0.6723.58
  3. Confirm WebAuthn is accessible
    In Chrome for Android, navigate to chrome://flags/#webauthn and check if the WebAuthn API is enabled. By default it is enabled.
    Affected if WebAuthn is enabled (default state) and the Chrome version is vulnerable as above
  4. Assess attack surface for HTML delivery
    Check if the Android device allows app installations from unknown sources in Settings > Security > Unknown sources, or if the user has a browser history that could be accessed by a local attacker.
    Affected if Unknown sources are enabled or the device has been compromised to deliver a crafted HTML page locally

You are affected if Chrome for Android is installed with a version below 130.0.6723.58 and the WebAuthn API is accessible (which it is by default).

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

Update Google Chrome for Android to version 130.0.6723.58 or later. In enterprise environments, deploy the update via mobile device management (MDM) policies to ensure all managed devices receive the patch.

Recommended fix High confidence

Chrome for Android version 130.0.6723.58 or later (stable channel)

  1. Verify the current Chrome version by navigating to chrome://settings/help or checking About Chrome in the app menu
  2. On Android, open the Google Play Store and search for Google Chrome
  3. Update Chrome to the latest version available (version 130.0.6723.58 or later)
  4. Alternatively, for enterprise-managed devices, use Google Play managed play store configurations to push the update
  5. After updating, verify the version shows 130.0.6723.58 or higher in chrome://settings/help
  6. Clear browser data if any unusual behavior persists after update
Caveat Minimal risk - Chrome stable updates maintain backwards compatibility; WebAuthentication API behavior changes may affect custom credential flows but are unlikely to break standard web usage

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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