Compact ColumnsApplication · Jenkins
CVE-2020-2195
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 Compact Columns Plugin 1.11 and earlier displays the unprocessed job description in tooltips, resulting in a stored cross-site scripting vulnerability that can be exploited by users with Job/Configure permission.
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 Compact Columns Plugin versions 1.11 and earlier displays unprocessed job descriptions in tooltips, allowing stored cross-site scripting (XSS) attacks. Users with Job/Configure permission can inject malicious scripts into job descriptions that execute when other users view the column tooltips.
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
Compact ColumnsApplication
<= 1.11CVSS 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 if Compact Columns Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Compact Columns', or check the $JENKINS_HOME/plugins directory for the compact-columns folderAffected if The plugin is present in the installation
-
Verify the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed, find Compact Columns and note the version number shown; alternatively, check the version file in $JENKINS_HOME/plugins/compact-columns/META-INF/MANIFEST.MFAffected if Version is 1.11 or earlier
-
Determine if Compact Columns are configured in any viewsOpen each Jenkins view configuration and check if the Compact Columns column type is added to the column list displayedAffected if At least one view uses Compact Columns to display job information
-
Inspect job descriptions for potential XSS payloadsReview the 'Description' field in Job > Configure for each job. Use Jenkins REST API: GET /job/JOBNAME/api/json?tree=description to retrieve descriptions programmatically and search for common XSS patterns like <script>, javascript:, onerror=, onload=Affected if Any job description contains unsanitized HTML or script tags that could execute in tooltips
You are affected if the Compact Columns Plugin version 1.11 or earlier is installed AND is configured in at least one view, regardless of whether malicious job descriptions currently exist in your environment
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 Jenkins Compact Columns Plugin to version 1.12 or later, which properly processes and sanitizes job descriptions before rendering them in tooltips.
Fix this in Compact Columns
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2195 — 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-2195 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