# CVE-2022-41231: Path traversal in Jenkins build-publisher Plugin

> Attackers with configure permissions can overwrite arbitrary configuration files on the Jenkins controller via path traversal, potentially escalating privileges.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/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:** No
- **Published:** 21 Sep 2022
- **Updated:** 28 May 2025
- **Also known as:** GHSA-jrqh-c9v8-ccx9

## What is CVE-2022-41231?

CVE-2022-41231 is a medium-severity path traversal vulnerability in Jenkins Build-Publisher Plugin, published on 21 Sep 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 Build-Publisher Plugin 1.22 and earlier allows attackers with Item/Configure permission to create or replace any config.xml file on the Jenkins controller file system by providing a crafted file name to an API endpoint.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:build-publisher` | Maven | All versions to 1.22 | None |
| `org.jenkins-ci.plugins:build-publisher` | Maven | All versions to 1.22 | None |

Products: Jenkins Build-Publisher.

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

No fix has been published for CVE-2022-41231 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41231 being exploited?

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

## Other vulnerabilities in Jenkins Build-Publisher Plugin

- [CVE-2022-41232](https://insights.sbomify.com/CVE-2022-41232/): Jenkins build-publisher plugin vulnerable to cross-site request forgery (high 8.0)
- [CVE-2017-1000387](https://insights.sbomify.com/CVE-2017-1000387/): Jenkins Build-Publisher plugin has Insufficiently Protected Credentials (high 7.8)
- [CVE-2022-41230](https://insights.sbomify.com/CVE-2022-41230/): Missing permission check in Jenkins build-publisher Plugin (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41231 is a medium-severity path traversal vulnerability in Jenkins Build-Publisher Plugin, published on 21 Sep 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-41231 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:build-publisher (Maven): affected all versions up to 1.22; no fix listed
- org.jenkins-ci.plugins:build-publisher (Maven): affected all versions up to 1.22; no fix listed

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

## Sources

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

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