ChromeWeb browser · Google
CVE-2020-6445
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 trusted types in Google Chrome prior to 81.0.4044.92 allowed a remote 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 confidenceA flaw in Google Chrome's Trusted Types implementation allowed remote attackers to bypass Content Security Policy (CSP) restrictions through specially crafted HTML pages. Trusted Types are designed to prevent DOM-based XSS by enforcing strict type checking on potentially dangerous DOM APIs, but insufficient policy enforcement enabled CSP bypass.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 if Google Chrome is installedOpen terminal and run: which google-chrome or google-chrome --versionAffected if No Chrome binary is found, the system is not affected by this browser vulnerability
-
Determine installed Chrome versionRun: google-chrome --version or look in About Google Chrome in the browser menuAffected if Version number is lower than 81.0.4044.92 (e.g., 80.x or earlier)
-
Check Chrome version on Debian systemsRun: dpkg -l | grep google-chrome or apt policy google-chrome-stableAffected if Installed version on Debian 9 or 10 is lower than 81.0.4044.92
-
Check Chrome version on Fedora systemsRun: rpm -qa | grep google-chrome or dnf list installed google-chrome-stableAffected if Installed version on Fedora 30, 31, or 32 is lower than 81.0.4044.92
-
Check Chrome version on openSUSE systemsRun: rpm -qa | grep google-chrome or zypper search -i google-chromeAffected if Installed version on openSUSE Leap 15.1 or SLE 15 is lower than 81.0.4044.92
A user is affected if they run any Google Chrome version below 81.0.4044.92 on the listed Linux distributions or on any system where the browser version falls within the affected range.
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 obtain the patched Trusted Types implementation.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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-6445 — 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-6445 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