Clearcase ReleaseApplication · Jenkins
CVE-2020-2270
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 ClearCase Release Plugin 0.3 and earlier does not escape the composite baseline in badge tooltip, 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 ClearCase Release Plugin versions 0.3 and earlier fail to escape the composite baseline parameter when rendering it in a badge tooltip, allowing stored XSS injection. Attackers with Job/Configure permission can inject malicious JavaScript into the composite baseline field that 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
Clearcase ReleaseApplication
<= 0.3CVSS 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 ClearCase Release Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'ClearCase Release', or inspect the plugin file at $JENKINS_HOME/plugins/ for a clearcase-release.jpi fileAffected if Plugin is present in the Jenkins instance
-
Determine the installed plugin versionOn the Manage Plugins > Installed page, locate the ClearCase Release Plugin and record the version number shownAffected if Version is 0.3 or earlier (the vulnerable version range)
-
Identify jobs using the composite baseline featureReview job configurations that have the ClearCase Release Plugin configured, specifically look for the 'composite baseline' or similar parameter field in the job's build configurationAffected if Any job has a composite baseline value configured and the plugin version is <= 0.3
-
Assess who has Job/Configure permissionCheck Jenkins authorization matrix or per-project permissions to see which users or groups can configure jobs, particularly those using the ClearCase Release PluginAffected if Untrusted users have Job/Configure permission on jobs using this plugin
User is affected if ClearCase Release Plugin version 0.3 or earlier is installed AND composite baseline is being used in any job configuration, allowing an attacker with Job/Configure permission to inject malicious script.
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 to Jenkins ClearCase Release Plugin version 0.4 or later which includes proper escaping of the composite baseline in badge tooltips. Until upgraded, limit Job/Configure permission to trusted users only.
Fix this in Clearcase Release
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2270 — 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-2270 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