CVE-2020-15660
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 · uneditedMissing checks on Content-Type headers in geckodriver before 0.27.0 could lead to a CSRF vulnerability, that might, when paired with a specifically prepared request, lead to remote code execution.
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 confidenceMissing Content-Type header validation in geckodriver before version 0.27.0 enables CSRF attacks. When combined with specially crafted requests, this vulnerability could lead to remote code execution.
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< 0.27.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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 if geckodriver is installedRun 'geckodriver --version' or locate the geckodriver binary on your system (commonly in /usr/bin/, /usr/local/bin/, or a project vendor/ directory)Affected if geckodriver command is found and executable on the system
-
Determine the installed geckodriver versionExamine the version output from 'geckodriver --version' - the version number appears in the first line (e.g., geckodriver 0.26.0)Affected if The version displayed is below 0.27.0 (such as 0.26.0, 0.25.0, etc.)
-
Verify the feature is exposedConfirm geckodriver is running as a service and accepting HTTP requests (listening on a port, typically 4444 by default, or a custom port configured for WebDriver communication)Affected if geckodriver is actively running and accessible over HTTP to handle WebDriver requests
-
Confirm Content-Type validation is missingThis is determined by the version: versions prior to 0.27.0 lack proper Content-Type header validation in their HTTP request handlingAffected if The installed version is any release before 0.27.0, as this validation was not implemented in those versions
You are affected if geckodriver is installed and running with a version number lower than 0.27.0.
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.
dbcve · scoped0.27.0
Upgrade geckodriver to version 0.27.0 or later to implement proper Content-Type header validation.
geckodriver 0.27.0 or later
- 1. Identify the current geckodriver version in use (typically via 'geckodriver --version' command).
- 2. Download geckodriver version 0.27.0 or later from the official Mozilla GitHub releases page (github.com/mozilla/geckodriver/releases).
- 3. Replace the existing geckodriver binary with the new version.
- 4. Ensure the new geckodriver version is compatible with your Firefox browser version; refer to Mozilla's compatibility documentation if needed.
- 5. Verify the upgrade by running 'geckodriver --version' to confirm version 0.27.0 or higher is installed.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing4.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 $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15660 — 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-15660 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