ChromeWeb browser · Google
CVE-2020-15975
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 · uneditedInteger overflow in SwiftShader in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
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 confidenceInteger overflow in SwiftShader (Google's software WebGL renderer) in Chrome versions prior to 86.0.4240.75 allows a remote attacker to exploit heap corruption via a specially crafted HTML page, potentially leading to arbitrary 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
< 86.0.4240.75
FedoraOperating system
= 31= 32= 33
Debian LinuxOperating system
= 10.0= 15.0CVSS 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 if Google Chrome is installedOn Windows: Check for Chrome in Program Files or via registry. On Linux: Check for /usr/bin/google-chrome or /opt/google/chrome/google-chrome. On macOS: Check /Applications/Google Chrome.appAffected if Chrome is not found on the system - the vulnerability does not apply
-
Determine the installed Chrome versionOpen Chrome, go to chrome://settings/help, or run 'google-chrome --version' from command line, or check the executable propertiesAffected if Unable to determine version - further investigation needed
-
Compare installed version against vulnerable rangeCompare the detected version number to 86.0.4240.75 - versions below this threshold (such as 85.x.x.x, 84.x.x.x, etc.) are affectedAffected if Installed version is less than 86.0.4240.75 - the system is vulnerable to this integer overflow in SwiftShader
-
Identify if WebGL is accessible (attack vector verification)In Chrome, navigate to chrome://gpu/ and check if SwiftShader/WebGL is listed as available, or visit any WebGL-enabled website to confirm WebGL functionality is workingAffected if WebGL is disabled or unavailable - the specific attack vector via specially crafted HTML pages would not be reachable, though the vulnerable code still exists in the binary
A user is affected if Google Chrome is installed with a version lower than 86.0.4240.75 and WebGL functionality is accessible in the browser.
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.
From vendor data86.0.4240.75
Update Google Chrome to version 86.0.4240.75 or later to patch the vulnerability; enterprise environments should deploy the update via endpoint management tools and verify compliance.
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-2020-15975 — 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-2020-15975 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