# CVE-2020-2256: Stored XSS vulnerability in Pipeline Maven Integration Plugin via unescaped display name

> Stored XSS in Jenkins Maven plugin allows attackers with Job/Configure permission to execute scripts via upstream job display names.

- **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:** Yes
- **Published:** 16 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hq2h-9mc3-h6w2

## What is CVE-2020-2256?

CVE-2020-2256 is a medium-severity cross-site scripting vulnerability in Jenkins Pipeline Maven Integration 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 Pipeline Maven Integration Plugin 3.9.2 and earlier does not escape the upstream job's display name shown as part of a build cause, 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-2256?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:pipeline-maven. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:pipeline-maven` | Maven | All versions | 3.9.3 |
| `org.jenkins-ci.plugins:pipeline-maven` | Maven | All versions | 3.9.3 |

Products: Jenkins Pipeline Maven Integration.

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

Upgrade org.jenkins-ci.plugins:pipeline-maven to 3.9.3 or later.

## Is CVE-2020-2256 being exploited?

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

## Other vulnerabilities in Jenkins Pipeline Maven Integration Plugin

- [CVE-2019-10327](https://insights.sbomify.com/CVE-2019-10327/): XML External Entity processing vulnerability in Pipeline Maven Integration Jenkins Plugin (high 8.1)
- [CVE-2020-2233](https://insights.sbomify.com/CVE-2020-2233/): Missing permission check in Jenkins Pipeline Maven Integration Plugin allows enumerating credentials IDs (medium 6.5)
- [CVE-2020-2234](https://insights.sbomify.com/CVE-2020-2234/): Missing permission check in Jenkins Pipeline Maven Integration Plugin allow capturing credentials (medium 6.5)
- [CVE-2020-2235](https://insights.sbomify.com/CVE-2020-2235/): CSRF vulnerability in Jenkins Pipeline Maven Integration Plugin allow capturing credentials (medium 6.5)
- [CVE-2023-41934](https://insights.sbomify.com/CVE-2023-41934/): Improper masking of credentials in Jenkins Pipeline Maven Integration Plugin (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-2256 is a medium-severity cross-site scripting vulnerability in Jenkins Pipeline Maven Integration 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-2256 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:pipeline-maven (Maven): affected all versions; fixed in 3.9.3
- org.jenkins-ci.plugins:pipeline-maven (Maven): affected all versions; fixed in 3.9.3

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-2256/ (Markdown: https://insights.sbomify.com/CVE-2020-2256/index.md)
```

## Sources

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

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