ChromeWeb browser · Google
CVE-2020-15977
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 dialogs in Google Chrome on OS X prior to 86.0.4240.75 allowed a remote attacker to obtain potentially sensitive information from disk 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 confidenceThis is a client-side vulnerability in Google Chrome on macOS where insufficient data validation in dialog components allows a remote attacker to read potentially sensitive files from the local disk by tricking a user into visiting a crafted HTML page. The attacker exploits the dialog mechanism to access file system information that should not be exposed to web content.
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
< 86.0.4240.75
Debian LinuxOperating system
= 10.0
FedoraOperating system
= 31= 32= 33= 15.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 installedOn macOS, open Terminal and run: ls /Applications/ | grep -i chrome. Or check the version directly: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version 2>/dev/null || /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --product-version 2>/dev/nullAffected if Google Chrome is not found in Applications folder
-
Verify the Chrome version against affected rangeRun: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version. Compare the output to the affected version range: < 86.0.4240.75Affected if The installed version number is lower than 86.0.4240.75 (for example, 85.0.3987.132 or 86.0.4240.0)
-
Confirm the operating system is macOSRun: uname -s. The output should be DarwinAffected if The OS is not macOS (the vulnerability is specific to Chrome on macOS)
A user is affected if Google Chrome version lower than 86.0.4240.75 is installed on a macOS system, as the dialog vulnerability can be exploited to read local files.
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 data86.0.4240.75
Update Google Chrome to version 86.0.4240.75 or later on all macOS systems. For enterprise environments, deploy the update through centralized patch management and verify completion across the fleet.
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-15977 — 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-15977 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