# CVE-2022-29036: Cross-site Scripting in Jenkins Credentials Plugin

> Stored XSS in Jenkins Credentials Plugin allows attackers with Item/Configure permission to execute scripts via unescaped parameter names and descriptions.

- **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:** 12 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rvg5-f5fj-mxvg

## What is CVE-2022-29036?

CVE-2022-29036 is a medium-severity cross-site scripting vulnerability in Jenkins Credentials Plugin, published on 12 Apr 2022. 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 Credentials Plugin 1111.v35a_307992395 and earlier, except 1087.1089.v2f1b_9a_b_040e4, 1074.1076.v39c30cecb_0e2, and 2.6.1.1, does not escape the name and description of Credentials parameters on views displaying parameters, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.

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

## Which versions are affected by CVE-2022-29036?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:credentials` | Maven | All versions | 2.6.1.1 |
| `org.jenkins-ci.plugins:credentials` | Maven | All versions | 2.6.1.1 |
| `org.jenkins-ci.plugins:credentials` | Maven | From 1087.v16065d268466 | 1087.1089.v2f1b_9a_b_040e4 |
| `org.jenkins-ci.plugins:credentials` | Maven | From 1087.v16065d268466 | 1087.1089.v2f1b_9a_b_040e4 |
| `org.jenkins-ci.plugins:credentials` | Maven | From 1105 to 1111.v35a | None |
| `org.jenkins-ci.plugins:credentials` | Maven | From 1105 to 1111.v35a | None |
| `org.jenkins-ci.plugins:credentials` | Maven | From 2.6.2 | 1074.1076.v39c30cecb_0e2 |
| `org.jenkins-ci.plugins:credentials` | Maven | From 2.6.2 | 1074.1076.v39c30cecb_0e2 |

Products: Jenkins Credentials.

## How do I fix CVE-2022-29036?

Upgrade org.jenkins-ci.plugins:credentials to a fixed version for your release line: 2.6.1.1, 1087.1089.v2f1b_9a_b_040e4 or 1074.1076.v39c30cecb_0e2.

## Is CVE-2022-29036 being exploited?

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

## Other vulnerabilities in Jenkins Credentials Plugin

- [CVE-2024-47805](https://insights.sbomify.com/CVE-2024-47805/): Jenkins Credentials plugin reveals encrypted values of credentials to users with Extended Read permission (high 7.5)
- [CVE-2021-21648](https://insights.sbomify.com/CVE-2021-21648/): Cross-Site Request Forgery in Jenkins Credentials Plugin (medium 6.1)
- [CVE-2019-10320](https://insights.sbomify.com/CVE-2019-10320/): Insertion of Sensitive Information into Externally-Accessible File or Directory in Jenkins Credentials Plugin (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29036 and fix it if it is affected.

What it is: CVE-2022-29036 is a medium-severity cross-site scripting vulnerability in Jenkins Credentials Plugin, published on 12 Apr 2022. 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-2022-29036 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:credentials (Maven): affected all versions; fixed in 2.6.1.1
- org.jenkins-ci.plugins:credentials (Maven): affected all versions; fixed in 2.6.1.1
- org.jenkins-ci.plugins:credentials (Maven): affected from 1087.v16065d268466; fixed in 1087.1089.v2f1b_9a_b_040e4
- org.jenkins-ci.plugins:credentials (Maven): affected from 1087.v16065d268466; fixed in 1087.1089.v2f1b_9a_b_040e4
- org.jenkins-ci.plugins:credentials (Maven): affected from 1105 up to 1111.v35a; no fix listed
- org.jenkins-ci.plugins:credentials (Maven): affected from 1105 up to 1111.v35a; no fix listed
- org.jenkins-ci.plugins:credentials (Maven): affected from 2.6.2; fixed in 1074.1076.v39c30cecb_0e2
- org.jenkins-ci.plugins:credentials (Maven): affected from 2.6.2; fixed in 1074.1076.v39c30cecb_0e2

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

## Sources

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

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