# CVE-2022-25175: Jenkins Pipeline: Multibranch Plugin vulnerable to OS Command Injection

> Attackers with Item/Configure permission can execute arbitrary OS commands on the Jenkins controller via crafted SCM contents in the Multibranch Plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-pj84-qjm3-77mg

## What is CVE-2022-25175?

CVE-2022-25175 is a high-severity command injection vulnerability in Jenkins Pipeline: Multibranch Plugin, published on 15 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Pipeline: Multibranch Plugin 706.vd43c65dec013 and earlier uses the same checkout directories for distinct SCMs for the readTrusted step, allowing attackers with Item/Configure permission to invoke arbitrary OS commands on the controller through crafted SCM contents.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins.workflow:workflow-multibranch` | Maven | All versions | 707.v71c3f0a_6ccdb |
| `org.jenkins-ci.plugins.workflow:workflow-multibranch` | Maven | All versions | 707.v71c3f0a_6ccdb |

Products: Jenkins Pipeline\.

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

Upgrade org.jenkins-ci.plugins.workflow:workflow-multibranch to 707.v71c3f0a_6ccdb or later.

## Is CVE-2022-25175 being exploited?

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

Public exploit code:

- https://github.com/shoucheng3/jenkinsci__workflow-multibranch-plugin_CVE-2022-25175_706-vd43c65dec013 (github_poc): https://github.com/shoucheng3/jenkinsci__workflow-multibranch-plugin_CVE-2022-25175_706-vd43c65dec013

## Other vulnerabilities in Jenkins Pipeline: Multibranch 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-2022-25175 and fix it if it is affected.

What it is: CVE-2022-25175 is a high-severity command injection vulnerability in Jenkins Pipeline: Multibranch Plugin, published on 15 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25175 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins.workflow:workflow-multibranch (Maven): affected all versions; fixed in 707.v71c3f0a_6ccdb
- org.jenkins-ci.plugins.workflow:workflow-multibranch (Maven): affected all versions; fixed in 707.v71c3f0a_6ccdb

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

## Sources

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

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