JenkinsApplication
CVE-2020-2160
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 2.227 and earlier, LTS 2.204.5 and earlier uses different representations of request URL paths, which allows attackers to craft URLs that allow bypassing CSRF protection of any target URL.
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 confidenceJenkins versions 2.227 and earlier, LTS 2.204.5 and earlier have a path normalization vulnerability where different representations of request URL paths are handled inconsistently. This inconsistency allows attackers to craft specially crafted URLs that bypass CSRF protection mechanisms, potentially allowing unauthorized actions on any target URL within the Jenkins instance.
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
JenkinsApplication
<= 2.204.5<= 2.227CVSS 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.
-
Identify installed Jenkins versionAccess the Jenkins web UI and look at the footer, or run 'java -jar jenkins.war --version' if you have CLI access, or check the 'jenkins' service version via package managerAffected if The version displayed is 2.204.5 or earlier for LTS, or 2.227 or earlier for weekly releases
-
Confirm LTS vs weekly release typeIn the Jenkins web UI footer, check if the version string contains 'LTS' - if not, it is a weekly releaseAffected if The version is LTS 2.204.5 or lower, or a weekly release 2.227 or lower
-
Verify CSRF protection is enabledNavigate to 'Manage Jenkins' > 'Configure Global Security' and check if 'Enable proxy compatibility' or 'Enable CSRF protection' is checked under 'CSRF Protection'Affected if CSRF protection is enabled AND the Jenkins version is in the affected range (2.204.5 or lower LTS, or 2.227 or lower weekly)
-
Check for suspicious access logsReview Jenkins access logs (typically in $JENKINS_HOME/access.log or application server logs) for URL paths with unusual encoding, double slashes, or encoded characters that may indicate exploitation attemptsAffected if Any log entries show crafted URL patterns that bypass CSRF tokens
You are affected if your Jenkins installation version is 2.204.5 or earlier (LTS) or 2.227 or earlier (weekly) and CSRF protection is enabled.
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 dataUpgrade to Jenkins 2.228 or LTS 2.204.6 or later, which corrects the URL path handling to ensure consistent representation and proper CSRF protection.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2160 — 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-2160 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