ChromeWeb browser · Google
CVE-2020-6456
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 validation of untrusted input in clipboard in Google Chrome prior to 81.0.4044.92 allowed a local attacker to bypass site isolation via crafted clipboard contents.
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 validation of untrusted input in Google Chrome's clipboard functionality allowed a local attacker to bypass site isolation by crafting malicious clipboard contents. The vulnerability existed in versions prior to 81.0.4044.92, where clipboard data was not properly validated before being processed.
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
< 81.0.4044.92
Debian LinuxOperating system
= 9.0= 10.0
FedoraOperating system
= 30= 31= 32= sle-15= 15.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 Google Chrome versionRun 'google-chrome --version' or 'google-chrome-stable --version' in terminal, or navigate to chrome://settings/help in the browser to view the versionAffected if Version is lower than 81.0.4044.92
-
Verify Chrome package installation pathCheck for Chrome binary at common locations: /usr/bin/google-chrome, /usr/bin/google-chrome-stable, or /opt/google/chrome/google-chromeAffected if Chrome is installed at any of these paths AND the version from step 1 is below 81.0.4044.92
-
Confirm clipboard feature is in useThis vulnerability affects clipboard handling; any use of copy/paste functionality within Chrome could trigger the flaw. No special configuration needed - the vulnerable code path exists in standard clipboard operationsAffected if Chrome version is vulnerable AND clipboard functionality is used (default behavior)
-
Check Debian package version if applicableOn Debian 9 or 10 systems, run 'dpkg -l | grep google-chrome' or check /var/log/apt/history.log for chrome package installation recordsAffected if Running Debian 9.0 or 10.0 with google-chrome package version below 81.0.4044.92
-
Check Fedora/openSUSE package version if applicableOn affected Fedora (30,31,32) or openSUSE (Leap 15.1, Backports sle-15) systems, run 'rpm -q google-chrome-stable' or check package manager logsAffected if Running an affected Fedora or openSUSE distribution with google-chrome-stable package version below 81.0.4044.92
You are affected if Google Chrome version 81.0.4044.92 or later is NOT installed on your system, regardless of operating system, because the vulnerability exists in the clipboard handling code of older versions.
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 data81.0.4044.92
Upgrade Google Chrome to version 81.0.4044.92 or later to address the insufficient input validation in the clipboard handler.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6456 — 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-6456 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