ChromeWeb browser · Google
CVE-2020-6439
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 navigations in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to bypass security UI 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 navigations in Google Chrome prior to version 81.0.4044.92 allows a remote attacker to bypass security UI (such as address bar origin display or security indicators) via a crafted HTML page. This is a client-side browser vulnerability affecting navigation policy handling.
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
- 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 installed Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' in terminal to see the exact version numberAffected if Version is less than 81.0.4044.92 (for example, 81.0.4044.91 or earlier)
-
Identify Chrome distribution packageOn Debian run 'dpkg -l | grep chrome' or check /opt/google/chrome; on Fedora run 'rpm -qa | grep chrome'; on openSUSE run 'rpm -qa | grep chrome'Affected if A Chrome package from the distribution repositories is installed and its bundled version is below 81.0.4044.92
-
Check Chromium browser version if Chrome not installedRun 'chromium --version' or 'chromium-browser --version' to check if a Chromium-based browser is installedAffected if Chromium-based browser version is less than 81.0.4044.92 (note: this vulnerability affects Chrome specifically but may impact Chromium builds)
-
Verify navigation security UI behaviorLoad a crafted test page that performs suspicious frame navigations and observe whether the address bar origin and security indicators update correctlyAffected if The address bar fails to update the origin or security indicators during certain navigation sequences, allowing spoofing of the page origin
A user is affected if their installed Chrome version is below 81.0.4044.92, or if a distribution-packaged Chrome/Chromium bundle with a version below that threshold is in use.
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
Update Google Chrome to version 81.0.4044.92 or later to remediate this vulnerability. Organizations should deploy browser updates through their patch management systems.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6439 — 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-6439 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