Computer QueueApplication · Jenkins
CVE-2020-2259
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 computer-queue-plugin Plugin 1.5 and earlier does not escape the agent name in tooltips, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Agent/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 computer-queue-plugin versions 1.5 and earlier fails to properly escape agent names when rendering them in tooltips, resulting in a stored cross-site scripting (XSS) vulnerability. An attacker with Agent/Configure permission can inject malicious JavaScript that executes when other users view the affected agent information.
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
Computer QueueApplication
<= 1.5CVSS 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.
-
Verify computer-queue-plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'computer-queue' or check the plugin directory $JENKINS_HOME/plugins for computer-queue pluginAffected if The plugin appears in the installed plugins list with version 1.5 or earlier
-
Check the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed, locate the computer-queue-plugin and note the version number displayedAffected if The version listed is 1.5 or any version lower than 1.5
-
Confirm agents are configuredNavigate to Manage Jenkins > Manage Nodes and check if any permanent agents or cloud agents are definedAffected if At least one agent/node is configured in Jenkins
-
Verify Agent/Configure permission assignmentsGo to Manage Jenkins > Manage Users and check which users or groups have the Agent/Configure permission in the authorization matrix or matrix-based security settingsAffected if Any user or group other than administrators has the Agent/Configure permission enabled
You are affected if the computer-queue-plugin version is 1.5 or earlier, agents are configured in Jenkins, and untrusted users have Agent/Configure permission, as the XSS vulnerability can be exploited through agent name 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 dataUpgrade the computer-queue-plugin to version 1.6 or later, which includes proper escaping of agent names in tooltips.
Fix this in Computer Queue
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-2259 — 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-2259 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