dbcve.org
ChromeWeb browser · Google

CVE-2020-6546

HIGH · 7.8 CVSS v3.1 Published 2020-09-21
Fix available
A fix is available. Upgrade to 84.0.4147.125 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Inappropriate implementation in installer in Google Chrome prior to 84.0.4147.125 allowed a local attacker to potentially elevate privilege via a crafted filesystem.

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 confidence

Google Chrome installer prior to version 84.0.4147.125 contained an inappropriate implementation flaw that allowed a local attacker to manipulate the installation process through a crafted filesystem, potentially elevating privileges on the affected system.

MitigationUpgrade Google Chrome to version 84.0.4147.125 or later. Organizations should deploy the updated browser version through their standard patch management processes.

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
Affected:< 84.0.4147.125
Debian LinuxOperating system
Affected:= 10.0
FedoraOperating system
Affected:= 33

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Google Chrome version
    Open Google Chrome, click the three-dot menu, select Help, then About Google Chrome. Alternatively, run 'google-chrome --version' or 'chrome --version' from command line.
    Affected if Version is less than 84.0.4147.125 or the version cannot be determined (older installation)
  2. Confirm operating system is Debian 10 or Fedora 33
    Run 'cat /etc/os-release' and look for VERSION_ID="10" (Debian) or VERSION_ID="33" (Fedora) in the output.
    Affected if The system is Debian 10.0 or Fedora 33 and Chrome version is below 84.0.4147.125
  3. Verify Chrome is installed via system package manager
    On Debian-based systems, run 'dpkg -l | grep google-chrome' or 'apt list --installed | grep chrome'. On Fedora, run 'rpm -qa | grep chrome'.
    Affected if Chrome installed via package manager on affected OS versions with vulnerable version number

You are affected if Google Chrome with version below 84.0.4147.125 is installed on Debian 10.0 or Fedora 33, and a local attacker with filesystem access could manipulate the installer process.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 84.0.4147.125 or later
Fixed in 84.0.4147.125
Interim mitigation

Upgrade Google Chrome to version 84.0.4147.125 or later. Organizations should deploy the updated browser version through their standard patch management processes.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6546 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-6546 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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