# CVE-2022-43407: CSRF protection for any URL can be bypassed in Jenkins Pipeline: Input Step Plugin

> Attackers can bypass CSRF protection in Jenkins by manipulating input step IDs, requiring the ability to configure Pipelines.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Oct 2022
- **Updated:** 8 May 2025
- **Also known as:** GHSA-g66m-fqxf-3w35

## What is CVE-2022-43407?

CVE-2022-43407 is a high-severity vulnerability in Jenkins Pipeline: Input Step Plugin, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Jenkins Pipeline: Input Step Plugin 451.vf1a_a_4f405289 and earlier does not restrict or sanitize the optionally specified ID of the 'input' step, which is used for the URLs that process user interactions for the given 'input' step (proceed or abort) and is not correctly encoded, allowing attackers able to configure Pipelines to have Jenkins build URLs from 'input' step IDs that would bypass the CSRF protection of any target URL in Jenkins when the 'input' step is interacted with.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

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 | 456.vd8a_957db_5b_e9 |
| `org.jenkins-ci.plugins:pipeline-input-step` | Maven | All versions | 456.vd8a_957db_5b_e9 |

Products: Jenkins Pipeline\.

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

Upgrade org.jenkins-ci.plugins:pipeline-input-step to 456.vd8a_957db_5b_e9 or later.

## Is CVE-2022-43407 being exploited?

There is no known exploitation of CVE-2022-43407 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-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)
- [CVE-2022-25174](https://insights.sbomify.com/CVE-2022-25174/): Improper Neutralization of Special Elements used in an OS Command in Jenkins Pipeline: Shared Groovy Libraries Plugin (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-43407 is a high-severity vulnerability in Jenkins Pipeline: Input Step Plugin, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-43407 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 456.vd8a_957db_5b_e9
- org.jenkins-ci.plugins:pipeline-input-step (Maven): affected all versions; fixed in 456.vd8a_957db_5b_e9

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

## Sources

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

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