ChromeWeb browser · Google
CVE-2020-15983
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 · uneditedInsufficient data validation in webUI in Google Chrome on ChromeOS prior to 86.0.4240.75 allowed a local attacker to bypass content security policy 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 confidenceInsufficient data validation in the webUI component of Google Chrome on ChromeOS prior to version 86.0.4240.75 allowed a local attacker to bypass content security policy (CSP) protections by using a crafted HTML page. This is a client-side vulnerability specific to ChromeOS that enables CSP bypass, potentially allowing execution of malicious scripts or unauthorized content loading.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the operating systemRun 'uname -a' or check system information to confirm if the system is ChromeOS. This vulnerability is specific to ChromeOS.Affected if The system is running ChromeOS and uses the affected Chrome version.
-
Check installed Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' in the terminal to determine the installed Chrome version.Affected if The installed Chrome version is lower than 86.0.4240.75.
-
Verify Chrome package version on Linux distributionsFor Fedora, run 'dnf list installed | grep chrome'. For Debian, run 'dpkg -l | grep google-chrome'. For openSUSE, run 'rpm -qa | grep chrome'. Compare the installed version against the vulnerable range.Affected if The installed package version corresponds to Chrome versions below 86.0.4240.75.
-
Confirm webUI component accessibilityThe vulnerability exists in the webUI component. No specific configuration check is needed as the flaw is in how the component handles crafted HTML pages. The check is satisfied if Chrome is running and accessible.Affected if Chrome is running and accessible on the system.
You are affected if you are running Google Chrome on ChromeOS (or the listed Linux distributions) with a version lower than 86.0.4240.75.
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 on ChromeOS devices to version 86.0.4240.75 or later to address the insufficient data validation in the webUI. For enterprise environments, deploy the update via MDM or patch management tools and verify compliance.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15983 — 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-15983 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