ChromeWeb browser · Google
CVE-2020-6484
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 ChromeDriver in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a crafted request.
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 confidenceInsufficient data validation in ChromeDriver (the WebDriver server for Chromium) allowed a remote attacker to bypass navigation restrictions via crafted HTTP requests. This vulnerability in the ChromeDriver server prior to version 83.0.4103.61 could allow malicious websites or external actors to manipulate browser navigation beyond intended WebDriver protocol constraints.
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.
-
Locate ChromeDriver executableRun 'which chromedriver' on Linux or search for chromedriver.exe on Windows. Check common paths: /usr/bin/chromedriver, /usr/local/bin/chromedriver, or C:\Program Files\chromedriver.exeAffected if ChromeDriver is found on the system
-
Determine ChromeDriver versionRun 'chromedriver --version' or 'chromedriver -v' to print the version numberAffected if Version shown is lower than 83.0.4103.61 (for example, 83.0.4103.0 or earlier)
-
Check if ChromeDriver server is runningRun 'netstat -tlnp | grep 9515' or 'ss -tlnp | grep 9515' to see if ChromeDriver is listening on port 9515 (default WebDriver port)Affected if ChromeDriver is listening on a network port and is accessible
-
Verify Chrome browser versionRun 'google-chrome --version' or 'chrome --version' to check the installed Chrome versionAffected if Chrome version is below 83.0.4103.61 (note: ChromeDriver and Chrome versions should match)
-
Assess network exposureReview firewall rules and service configurations to determine if ChromeDriver port 9515 is exposed to untrusted networks or accessible from remote hostsAffected if ChromeDriver server port is accessible from outside the local host or from untrusted networks
You are affected if ChromeDriver version is below 83.0.4103.61 AND the ChromeDriver server is running and accessible (locally or over network), since an attacker could send crafted HTTP requests to manipulate browser navigation.
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 ChromeDriver to version 83.0.4103.61 or later. Ensure ChromeDriver versions are synchronized with Chrome browser versions and restrict network access to ChromeDriver servers in production environments.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6484 — 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-6484 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