ChromeWeb browser · Google
CVE-2020-6491
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 site information in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof security UI via a crafted domain name.
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 confidenceThis is a UI spoofing vulnerability in Google Chrome caused by insufficient data validation when processing site information. A remote attacker can craft a malicious domain name to spoof security UI indicators (such as the address bar, lock icon, or HTTPS indicators), potentially tricking users into believing they are on a legitimate secure site.
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
< 83.0.4103.61
Debian LinuxOperating system
= 9.0= 10.0
FedoraOperating system
= 31= 32= 15.0= 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.
-
Determine installed Chrome versionOpen a terminal and run `google-chrome --version` or `chrome --version`. On some systems you may need to navigate to /opt/google/chrome/ and run `./google-chrome --version`.Affected if The command returns a version number lower than 83.0.4103.61 (for example, 83.0.4103.60 or earlier)
-
Verify via package manager (Debian)If installed via apt, run `dpkg -l | grep google-chrome` or `apt show google-chrome` to see the installed package version.Affected if The displayed version is less than 83.0.4103.61-1
-
Verify via package manager (Fedora)If installed via dnf, run `dnf info google-chrome` to see the installed package version.Affected if The displayed version is less than 83.0.4103.61-1
-
Verify via package manager (openSUSE)If installed via zypper, run `zypper info google-chrome` to see the installed package version.Affected if The displayed version is less than 83.0.4103.61-1
-
Check about dialog (alternative)Open Chrome, click the three-dot menu, go to Help, then About Google Chrome. The version number is displayed on that page.Affected if The version shown is 83.0.4103.60 or earlier
You are affected if your installed Google Chrome version is lower than 83.0.4103.61, regardless of which Linux distribution or packaging method was used to install it.
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 data83.0.4103.61
Update Google Chrome to version 83.0.4103.61 or later. Users should also be educated to verify the full URL in the address bar, not just rely on visual security indicators.
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-6491 — 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-6491 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