# CVE-2023-41930: Path traversal in Jenkins Job Configuration History Plugin

> Attackers can manipulate configuration history entries via the name parameter, potentially reading or modifying unauthorized data in Jenkins.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 6 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-c7r5-cww9-64q6

## What is CVE-2023-41930?

CVE-2023-41930 is a medium-severity path traversal vulnerability in Jenkins Job Configuration History Plugin, published on 6 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Job Configuration History Plugin 1227.v7a_79fc4dc01f and earlier does not restrict the 'name' query parameter when rendering a history entry, allowing attackers to have Jenkins render a manipulated configuration history that was not created by the plugin.

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

## Which versions are affected by CVE-2023-41930?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:jobConfigHistory` | Maven | All versions | 1229.v3039470161a_d |
| `org.jenkins-ci.plugins:jobConfigHistory` | Maven | All versions | 1229.v3039470161a_d |

Products: Jenkins Job Configuration History.

## How do I fix CVE-2023-41930?

Upgrade org.jenkins-ci.plugins:jobConfigHistory to 1229.v3039470161a_d or later.

## Is CVE-2023-41930 being exploited?

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

## Other vulnerabilities in Jenkins Job Configuration History Plugin

- [CVE-2023-41933](https://insights.sbomify.com/CVE-2023-41933/): Job Configuration History Plugin's path traversal allows exploiting XXE vulnerability (high 8.8)
- [CVE-2023-41932](https://insights.sbomify.com/CVE-2023-41932/): Path traversal allows exploiting XXE vulnerability in Jenkins Job Configuration History Plugin (medium 6.5)
- [CVE-2023-41931](https://insights.sbomify.com/CVE-2023-41931/): XSS vulnerability in Jenkins Job Configuration History Plugin (medium 5.4)
- [CVE-2022-38664](https://insights.sbomify.com/CVE-2022-38664/): Cross-site Scripting in Jenkins Job Configuration History Plugin (medium 5.4)
- [CVE-2026-57287](https://insights.sbomify.com/CVE-2026-57287/): Jenkins Job Configuration History Plugin doesn't redact encrypted values of secrets in job and agent configurations (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41930 and fix it if it is affected.

What it is: CVE-2023-41930 is a medium-severity path traversal vulnerability in Jenkins Job Configuration History Plugin, published on 6 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-41930 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:jobConfigHistory (Maven): affected all versions; fixed in 1229.v3039470161a_d
- org.jenkins-ci.plugins:jobConfigHistory (Maven): affected all versions; fixed in 1229.v3039470161a_d

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

## Sources

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

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