# CVE-2020-2270: Stored XSS vulnerability in ClearCase Release Plugin

> Stored XSS in Jenkins ClearCase Release Plugin allows attackers with Job/Configure permission to execute scripts in victim browsers.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2c84-35rv-6q3f

## What is CVE-2020-2270?

CVE-2020-2270 is a medium-severity cross-site scripting vulnerability in Jenkins ClearCase Release Plugin, published on 16 Sep 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Jenkins 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2020-2270?

2 open source packages ship an affected version, including org.jvnet.hudson.plugins:clearcase-release. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jvnet.hudson.plugins:clearcase-release` | Maven | All versions to 0.3 | None |
| `org.jvnet.hudson.plugins:clearcase-release` | Maven | All versions to 0.3 | None |

Products: Jenkins Clearcase Release.

## How do I fix CVE-2020-2270?

No fix has been published for CVE-2020-2270 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-2270 being exploited?

There is no known exploitation of CVE-2020-2270 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-2270 and fix it if it is affected.

What it is: CVE-2020-2270 is a medium-severity cross-site scripting vulnerability in Jenkins ClearCase Release Plugin, published on 16 Sep 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-2270 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jvnet.hudson.plugins:clearcase-release (Maven): affected all versions up to 0.3; no fix listed
- org.jvnet.hudson.plugins:clearcase-release (Maven): affected all versions up to 0.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-2270/ (Markdown: https://insights.sbomify.com/CVE-2020-2270/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-2270
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-2270
- OSV: https://osv.dev/vulnerability/CVE-2020-2270

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-2270/
Summaries are generated and may contain mistakes; the official description above is the record.