ChromeWeb browser · Google
CVE-2024-10487
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 · uneditedOut of bounds write in Dawn in Google Chrome prior to 130.0.6723.92 allowed a remote attacker to 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 · high confidenceOut-of-bounds write vulnerability in Dawn (Google's WebGPU implementation) in Google Chrome prior to version 130.0.6723.92. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, allowing memory corruption and potential code execution.
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
< 130.0.6723.92CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrome versionOpen Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on this page.Affected if Version shown is less than 130.0.6723.92
-
Confirm WebGPU access is possibleWebGPU is enabled by default in Chrome. To verify, visit chrome://gpu/ and look for 'WebGPU' in the 'Graphics Feature Status' list. If it shows 'Hardware accelerated' or 'Software only, not hardware accelerated', WebGPU is available.Affected if WebGPU is listed as available (not explicitly disabled via policy)
-
Determine user exposureConsider whether users in your environment have the ability to visit arbitrary web pages. This vulnerability is triggerable via a crafted HTML page, so any user who can browse the web is potentially exposed.Affected if Users can browse arbitrary websites and Chrome version is below 130.0.6723.92
You are affected if Chrome is installed at a version lower than 130.0.6723.92 and WebGPU is not explicitly disabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped130.0.6723.92
Upgrade Google Chrome to version 130.0.6723.92 or later. For systems where immediate patching is not feasible, disable WebGPU via Chrome enterprise policies or consider network-level restrictions until patching can be completed.
130.0.6723.92 or later
- Open Google Chrome browser
- Click the three-dot menu icon in the top-right corner
- Select 'Help' and then 'About Google Chrome'
- The browser will check for updates and automatically download version 130.0.6723.92 or later
- Click 'Relaunch' to restart Chrome and apply the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10487 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10487 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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