ChromeWeb browser · Google
CVE-2020-6477
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 · uneditedInappropriate implementation in installer in Google Chrome on OS X prior to 83.0.4103.61 allowed a local attacker to perform privilege escalation via a crafted file.
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 confidenceA local privilege escalation vulnerability existed in the Google Chrome installer for OS X prior to version 83.0.4103.61. An attacker with local file system access could craft malicious installer files to trigger improper file handling or execution flow, potentially gaining elevated privileges on the system.
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
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome version on the systemOn Mac OS X: Open Terminal and run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' or check 'About Google Chrome' in the Chrome menu. On Linux: Run 'google-chrome --version' or 'chromium --version' depending on the package installed.Affected if The installed version is earlier than 83.0.4103.61
-
Identify Chrome installer remnants on the systemSearch for Chrome installer DMG files, PKG files, or installer scripts in common locations such as ~/Downloads, /tmp, or the original installer application bundle in /Applications.Affected if A Chrome installer older than version 83.0.4103.61 exists on the file system and is accessible to local users
-
Verify the package installation source on Linux systemsOn Fedora: Run 'rpm -qa | grep -i chrome'. On openSUSE: Run 'rpm -qa | grep -i chrome' or check installed packages via 'zypper list|grep chrome'.Affected if Chrome packages from the affected Fedora 31, Fedora 32, openSUSE 15.0, or openSUSE 15.1 repositories are installed
-
Check for presence of the Chrome installer application bundleOn OS X, examine /Applications for 'Google Chrome Installer.app' and check its Info.plist or bundle version, or examine any DMG files mounted or stored on the system.Affected if A Google Chrome installer application bundle prior to version 83.0.4103.61 is present on the system
A system is affected if Google Chrome or its installer with a version earlier than 83.0.4103.61 is installed or present, and an attacker has local file system access to exploit the installer's improper file handling.
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
Upgrade Google Chrome to version 83.0.4103.61 or later on all affected OS X systems. Apply OS X system updates and follow least-privilege principles to limit local attacker access to the file system.
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-6477 — 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-6477 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