Custom Job IconApplication · Jenkins
CVE-2020-2264
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 Custom Job Icon Plugin 0.2 and earlier does not escape the job descriptions in tooltips, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers 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 confidenceThe Jenkins Custom Job Icon Plugin versions 0.2 and earlier fails to escape job descriptions when rendering them as tooltips, creating a stored cross-site scripting (XSS) vulnerability. Attackers with Job/Configure permission can inject malicious JavaScript into job descriptions that executes when other users view the job icon tooltip.
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
Custom Job IconApplication
<= 0.2CVSS 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.
-
Confirm Custom Job Icon Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or inspect $JENKINS_HOME/plugins for a directory named 'custom-job-icon' or similar. Alternatively, use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins 2>/dev/null | grep -i 'custom.*job.*icon'Affected if The plugin directory exists or the plugin appears in the plugin list
-
Identify the installed plugin versionCheck the $JENKINS_HOME/plugins/custom-job-icon/META-INF/MANIFEST.MF file for the Plugin-Version attribute, or view the plugin details in Manage Jenkins > Manage Plugins > Installed > Custom Job IconAffected if The version listed is 0.2 or lower
-
Verify if any untrusted users have Job/Configure permissionNavigate to Manage Jenkins > Manage and Assign Users/Roles and review which users or groups have the Job/Configure permission in the configured security realm and authorization strategyAffected if Users other than trusted administrators have Job/Configure permission
-
Inspect job configurations for unsanitized descriptionsReview job config.xml files in $JENKINS_HOME/jobs/<jobname>/config.xml, specifically look for the <description> field that could contain unsanitized HTML or script tagsAffected if Job descriptions contain raw HTML, script tags, or JavaScript event handlers that would execute in a tooltip
You are affected if the Custom Job Icon Plugin version 0.2 or earlier is installed AND users with Job/Configure permission can inject script content into job descriptions that render as tooltips.
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 Custom Job Icon Plugin to a version after 0.2 that properly escapes job descriptions in tooltips, or restrict Job/Configure permission to trusted users only until a patch is available.
Fix this in Custom Job Icon
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2264 — 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-2264 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