# CVE-2022-29049: Promotion names in Jenkins promoted builds Plugin are not validated when using Job DSL

> Attackers with Job/Configure permission can inject malicious scripts via unsafe promotion names in Jenkins promoted builds 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:** 12 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jmxr-w2jc-qp7w

## What is CVE-2022-29049?

CVE-2022-29049 is a medium-severity cross-site scripting vulnerability in Jenkins promoted builds 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 promoted builds Plugin 873.v6149db_d64130 and earlier, except 3.10.1, does not validate the names of promotions defined in Job DSL, allowing attackers with Job/Configure permission to create a promotion with an unsafe name.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:promoted-builds` | Maven | All versions | 3.10.1 |
| `org.jenkins-ci.plugins:promoted-builds` | Maven | All versions | 3.10.1 |
| `org.jenkins-ci.plugins:promoted-builds` | Maven | From 3.11 | 876.v99d29788b |
| `org.jenkins-ci.plugins:promoted-builds` | Maven | From 3.11 | 876.v99d29788b |

Products: Jenkins Promoted Builds.

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

Upgrade org.jenkins-ci.plugins:promoted-builds to a fixed version for your release line: 3.10.1 or 876.v99d29788b.

## Is CVE-2022-29049 being exploited?

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

## Other vulnerabilities in Jenkins promoted builds Plugin

- [CVE-2022-30965](https://insights.sbomify.com/CVE-2022-30965/): Stored Cross-site Scripting vulnerabilities in Jenkins promoted Builds (Simple) plugin providing additional parameter types (medium 5.4)
- [CVE-2022-29045](https://insights.sbomify.com/CVE-2022-29045/): Stored Cross-site Scripting vulnerability in Jenkins Promoted Builds Plugin (medium 5.4)
- [CVE-2021-21641](https://insights.sbomify.com/CVE-2021-21641/): CSRF vulnerability in Jenkins promoted builds Plugin (medium 4.3)
- [CVE-2018-1000114](https://insights.sbomify.com/CVE-2018-1000114/): Jenkins Promoted Builds Plugin allowed unauthorized users to run some promotion processes (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29049 is a medium-severity cross-site scripting vulnerability in Jenkins promoted builds 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-29049 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:promoted-builds (Maven): affected all versions; fixed in 3.10.1
- org.jenkins-ci.plugins:promoted-builds (Maven): affected all versions; fixed in 3.10.1
- org.jenkins-ci.plugins:promoted-builds (Maven): affected from 3.11; fixed in 876.v99d29788b
- org.jenkins-ci.plugins:promoted-builds (Maven): affected from 3.11; fixed in 876.v99d29788b

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

## Sources

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

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