# CVE-2023-32977: Jenkins Pipeline: Job Plugin vulnerable to stored Cross-site Scripting

> Attackers can inject malicious scripts via build display names, leading to stored XSS in Jenkins Pipeline: Job Plugin.

- **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 May 2023
- **Updated:** 23 Jan 2025
- **Also known as:** GHSA-2wvv-phhw-qvmc

## What is CVE-2023-32977?

CVE-2023-32977 is a medium-severity cross-site scripting vulnerability in Jenkins Pipeline: Job Plugin, published on 16 May 2023. 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: Job Plugin does not escape the display name of the build that caused an earlier build to be aborted, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to set build display names immediately.

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

## Which versions are affected by CVE-2023-32977?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins.workflow:workflow-job` | Maven | All versions | 1295.v395eb |
| `org.jenkins-ci.plugins.workflow:workflow-job` | Maven | All versions | 1295.v395eb |

Products: Jenkins Pipeline\.

## How do I fix CVE-2023-32977?

Upgrade org.jenkins-ci.plugins.workflow:workflow-job to 1295.v395eb or later.

## Is CVE-2023-32977 being exploited?

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

## Other vulnerabilities in Jenkins Pipeline: Job Plugin

- [CVE-2019-1003030](https://insights.sbomify.com/CVE-2019-1003030/): Jenkins Matrix Project Plugin Remote Code Execution (critical 9.9, exploited in the wild)
- [CVE-2022-43402](https://insights.sbomify.com/CVE-2022-43402/): Jenkins Pipeline: Groovy Plugin allows sandbox protection bypass and arbitrary code execution (critical 9.9)
- [CVE-2019-1003041](https://insights.sbomify.com/CVE-2019-1003041/): Sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin (critical 9.8)
- [CVE-2022-43407](https://insights.sbomify.com/CVE-2022-43407/): CSRF protection for any URL can be bypassed in Jenkins Pipeline: Input Step Plugin (high 8.8)
- [CVE-2022-25173](https://insights.sbomify.com/CVE-2022-25173/): Improper Neutralization of Special Elements used in an OS Command in Jenkins Pipeline: Groovy Plugin (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32977 and fix it if it is affected.

What it is: CVE-2023-32977 is a medium-severity cross-site scripting vulnerability in Jenkins Pipeline: Job Plugin, published on 16 May 2023. 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-2023-32977 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins.workflow:workflow-job (Maven): affected all versions; fixed in 1295.v395eb
- org.jenkins-ci.plugins.workflow:workflow-job (Maven): affected all versions; fixed in 1295.v395eb

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

## Sources

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

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