JenkinsApplication
CVE-2020-2163
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 improperly processes HTML content of list view column headers, resulting in a stored XSS vulnerability exploitable by users able to control column headers.
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, and LTS 2.204.5 and earlier improperly process HTML content in list view column headers, allowing stored XSS. Attackers with ability to control column headers can inject malicious scripts that execute in other users' browsers viewing those lists.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 your Jenkins versionNavigate to Manage Jenkins > About Jenkins, or append /api/json?tree=version to your Jenkins URLAffected if The displayed version is 2.204.5 or earlier (LTS), or 2.227 or earlier (weekly)
-
Identify custom list viewsBrowse to each job and look for views other than the default 'All' view. Check for views using list view columns configured via the UIAffected if Custom list views exist that allow configuring custom columns
-
Review column header configurationsEdit a list view and inspect the 'Columns' section. Look for any custom column headers or column configurations that accept user-supplied textAffected if Custom column headers contain unsanitized HTML or JavaScript in the column configuration
-
Audit users with view configuration permissionsCheck Manage Jenkins > Manage Users and review which users have permissions to create or configure list views (typically users with Job/Configure permission)Affected if Users other than administrators can configure list view columns
-
Inspect column renderingView a list view in the browser, right-click and view page source, then search for the column headers. Check if HTML characters are rendered as-is rather than escapedAffected if Column headers display raw HTML tags or execute JavaScript when viewed
You are affected if your Jenkins version is 2.204.5 or earlier (LTS) or 2.227 or earlier AND users with view configuration permissions exist who could inject malicious scripts into column headers.
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 Jenkins to version 2.227+ or LTS 2.204.6+ to receive the patch, and validate that column header rendering properly escapes HTML content.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2163 — 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-2163 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