ReleaseApplication · Jenkins
CVE-2020-2292
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 Release Plugin 2.10.2 and earlier does not escape the release version in badge tooltip, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Release/Release 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 Release Plugin versions 2.10.2 and earlier fail to properly escape the release version parameter when rendering it in the badge tooltip. This allows an attacker with Release/Release permission to inject malicious JavaScript code through the release version field, which executes when other users view the badge.
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
ReleaseApplication
<= 2.10.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.
-
Identify if Jenkins Release Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Release' in the plugin list, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://[jenkins-url] list-plugins | grep ReleaseAffected if The plugin does not appear in the installed list (not affected)
-
Determine the installed version of Jenkins Release PluginIn the Manage Plugins > Installed view, locate the Release plugin and note the Version column; alternatively, check the plugin manifest file at $JENKINS_HOME/plugins/release.jpi/META-INF/MANIFEST.MF for the Plugin-Version attributeAffected if Version is 2.10.2 or lower (potentially affected)
-
Verify if Release/Release permission is assigned to any usersNavigate to Manage Jenkins > Configure Global Security > Authorization or to the specific job's configuration if using matrix-based authorization; check for users or groups granted the 'Release' permission under the Release PluginAffected if Any untrusted user has Release/Release permission and the plugin version is <= 2.10.2 (vulnerable)
-
Check if releases have been performed using the pluginReview build history for jobs configured with the Release plugin; look for builds that used the Release action, which would trigger the badge tooltip rendering with the release version parameterAffected if A release was performed with a release version value and the plugin version is <= 2.10.2 (exploited)
You are affected if the Jenkins Release Plugin version is 2.10.2 or earlier AND any user with Release/Release permission has performed a release, as the badge tooltip will render the unsanitized release version parameter allowing XSS.
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 Jenkins Release Plugin to version 2.10.3 or later which includes proper escaping of the release version in the badge tooltip. Until patched, restrict the Release/Release permission to only trusted users.
Fix this in Release
Scoped from the published advisory
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2292 — 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-2292 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