dbcve.org
ChromeWeb browser · Google

CVE-2024-6990

HIGH · 8.8 CVSS v3.1 Published 2024-08-01
Fix available
A fix is available. Upgrade to 127.0.6533.88 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
Uninitialized Use in Dawn in Google Chrome on Android prior to 127.0.6533.88 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: Critical)

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 · moderate confidence

An uninitialized memory use vulnerability in the Dawn WebGPU implementation in Google Chrome for Android allows a remote attacker to potentially perform out-of-bounds memory access via a crafted HTML page, potentially leading to information disclosure or code execution.

MitigationUpdate Google Chrome on Android to version 127.0.6533.88 or later; for enterprise deployments, ensure mobile device management policies enforce Chrome updates.

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

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. Identify Chrome for Android installation
    On the Android device, go to Settings > Apps > Google Chrome to confirm Chrome browser is installed. Alternatively, open the Play Store and search for Chrome to verify it's installed.
    Affected if Chrome for Android is present on the device
  2. Locate the installed Chrome version number
    On the Android device, open Chrome, tap the three-dot menu, go to Settings > About Chrome. The version number is displayed on this page (format: X.X.X.XXX).
    Affected if Unable to retrieve version number from the device
  3. Compare version against affected range
    Compare the retrieved version number to 127.0.6533.88. The vulnerability affects versions earlier than 127.0.6533.88. Ensure you compare all four version segments numerically.
    Affected if Installed version is less than 127.0.6533.88 (e.g., 127.0.6533.72, 126.0.6545.124, etc.)
  4. Determine WebGPU usage context
    Check if WebGPU is actively used or enabled in the organization. This vulnerability in Dawn's WebGPU implementation can be triggered when a user visits a malicious webpage that utilizes the WebGPU API.
    Affected if Users run Chrome for Android versions below 127.0.6533.88 and browse untrusted web content that leverages WebGPU

The environment is affected if Chrome for Android with a version lower than 127.0.6533.88 is installed and users can access web content, as the uninitialized use flaw in Dawn's WebGPU implementation can be triggered remotely via malicious HTML pages.

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

Update Google Chrome on Android to version 127.0.6533.88 or later; for enterprise deployments, ensure mobile device management policies enforce Chrome updates.

Recommended fix High confidence

127.0.6533.88

  1. Open Google Play Store on your Android device
  2. Search for "Google Chrome" or locate it in your installed apps
  3. If an update is available, tap the "Update" button to install Chrome version 127.0.6533.88 or later
  4. Alternatively, open Chrome > tap the three dots menu > go to Help > About Chrome > the browser will automatically check for and prompt you to install updates
  5. After updating, verify the version by going to Chrome > three dots menu > Help > About Chrome, which should show version 127.0.6533.88 or higher

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

Fix this in Chrome Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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