ChromeWeb browser · Google
CVE-2020-6420
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 policy enforcement in media in Google Chrome prior to 80.0.3987.132 allowed a remote attacker to bypass same origin 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 · moderate confidenceInsufficient policy enforcement in Google Chrome's media component allowed a remote attacker to bypass the same-origin policy via a crafted HTML page. This vulnerability in versions prior to 80.0.3987.132 could permit unauthorized access to media resources across different origins.
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
< 80.0.3987.132
Debian LinuxOperating system
= 9.0= 10.0
FedoraOperating system
= 30CVSS 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 Google Chrome versionOpen Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' or 'chrome --version' from command lineAffected if Version is lower than 80.0.3987.132
-
Check Chromium version on DebianRun 'chromium --version' or 'dpkg -l | grep chromium' on Debian systemsAffected if Version is lower than 80.0.3987.132 and OS is Debian 9.0 or 10.0
-
Check Chromium version on FedoraRun 'chromium --version' or 'rpm -q chromium' on Fedora systemsAffected if Version is lower than 80.0.3987.132 and OS is Fedora 30
-
Identify if browser is used to access cross-origin mediaReview browser usage patterns - the flaw is triggered when visiting crafted HTML pages that attempt to access media resources from a different originAffected if Users process untrusted web content and the browser version is vulnerable
You are affected if running Google Chrome or Chromium with version lower than 80.0.3987.132 on any operating system, with the specific known affected OS versions being Debian 9.0, 10.0, and Fedora 30.
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 data80.0.3987.132
Update Google Chrome to version 80.0.3987.132 or later to remediate this vulnerability. Organizations should ensure automated browser patching is enabled or deploy the update through enterprise management tools.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6420 — 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-6420 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