# CVE-2022-34177: Arbitrary file write vulnerability in Jenkins Pipeline: Input Step Plugin

> Attackers can create or replace arbitrary files on the Jenkins controller by exploiting unsanitized parameter names in Pipeline input steps.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-29q6-p2cg-4v23, RHSA-2022:9110

## What is CVE-2022-34177?

CVE-2022-34177 is a high-severity path traversal vulnerability in Jenkins Pipeline: Input Step Plugin, published on 22 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jenkins Pipeline: Input Step Plugin 448.v37cea_9a_10a_70 and earlier archives files uploaded for `file` parameters for Pipeline `input` steps on the controller as part of build metadata, using the parameter name without sanitization as a relative path inside a build-related directory, allowing attackers able to configure Pipelines to create or replace arbitrary files on the Jenkins controller file system with attacker-specified content.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:pipeline-input-step` | Maven | All versions | 449.v77f0e8b |
| `org.jenkins-ci.plugins:pipeline-input-step` | Maven | All versions | 449.v77f0e8b |
| `jenkins-2-plugins` | Red Hat:openshift:4.9::el8 | All versions | 0:4.9.1669894222-1.el8 |

Products: Jenkins Pipeline\.

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

Upgrade org.jenkins-ci.plugins:pipeline-input-step to 449.v77f0e8b or later.

## Is CVE-2022-34177 being exploited?

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

## Other vulnerabilities in Jenkins Pipeline: Input Step 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-34177 and fix it if it is affected.

What it is: CVE-2022-34177 is a high-severity path traversal vulnerability in Jenkins Pipeline: Input Step Plugin, published on 22 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34177 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:pipeline-input-step (Maven): affected all versions; fixed in 449.v77f0e8b
- org.jenkins-ci.plugins:pipeline-input-step (Maven): affected all versions; fixed in 449.v77f0e8b

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

## Sources

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

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