SeleniumApplication · Jenkins
CVE-2020-2196
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 · uneditedJenkins Selenium Plugin 3.141.59 and earlier has no CSRF protection for its HTTP endpoints, allowing attackers to perform all administrative actions provided by the plugin.
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 confidenceThe Jenkins Selenium Plugin versions 3.141.59 and earlier lacks CSRF (Cross-Site Request Forgery) protection on its HTTP endpoints. This vulnerability allows attackers to craft malicious requests that, when triggered by an authenticated administrator session, can execute administrative actions provided by the plugin without the user's consent.
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
SeleniumApplication
<= 3.141.59CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Jenkins is runningAccess the Jenkins dashboard (usually at http://yourserver:8080) and verify you can log in as an administrator.Affected if Jenkins is accessible without additional context
-
Check if Selenium Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://yourserver:8080 list-plugins to list installed plugins.Affected if Selenium plugin appears in the installed plugins list
-
Determine the Selenium Plugin versionIn the Manage Plugins > Installed tab, find the Selenium Plugin and note the version number displayed. Alternatively, check the plugin's manifest file in the Jenkins plugins directory (typically $JENKINS_HOME/plugins/selenium/WEB-INF/MANIFEST.MF).Affected if The displayed version is 3.141.59 or earlier
-
Verify CSRF protection is absent on Selenium endpointsInspect the Selenium plugin's HTTP endpoints by reviewing the plugin's源代码 if available, or test by attempting a POST request without a valid Jenkins crumb token to Selenium-related URLs (such as /selenium/...).Affected if POST requests to Selenium plugin endpoints succeed without requiring a valid CSRF crumb token
The environment is affected if the Selenium Plugin is installed and its version is 3.141.59 or earlier, making CSRF-protected endpoints vulnerable to unauthorized administrative actions.
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 dataUpdate the Jenkins Selenium Plugin to version 3.141.60 or later which includes CSRF protection. Additionally, review user permissions and follow Jenkins best practices for securing administrative endpoints.
Fix this in Selenium
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2196 — 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-2196 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