# CVE-2024-5273: Jenkins Report Info Plugin Path Traversal vulnerability

> Attackers with Item/Configure permission can read arbitrary files on the Jenkins controller by manipulating the workspace path in the Report Info Plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **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:** No
- **Published:** 24 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-cw5r-jx8r-9f7x

## What is CVE-2024-5273?

CVE-2024-5273 is a medium-severity path traversal vulnerability in Jenkins Report Info Plugin, published on 24 May 2024. 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 Report Info Plugin 1.2 and earlier does not perform path validation of the workspace directory while serving report files, allowing attackers with Item/Configure permission to retrieve Surefire failures, PMD violations, Findbugs bugs, and Checkstyle errors on the controller file system by editing the workspace path.

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

## Which versions are affected by CVE-2024-5273?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:report-info` | Maven | All versions to 1.2 | None |
| `org.jenkins-ci.plugins:report-info` | Maven | All versions to 1.2 | None |

Products: Jenkins Report Info.

## How do I fix CVE-2024-5273?

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

## Is CVE-2024-5273 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5273 and fix it if it is affected.

What it is: CVE-2024-5273 is a medium-severity path traversal vulnerability in Jenkins Report Info Plugin, published on 24 May 2024. 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-2024-5273 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:report-info (Maven): affected all versions up to 1.2; no fix listed
- org.jenkins-ci.plugins:report-info (Maven): affected all versions up to 1.2; 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-2024-5273/ (Markdown: https://insights.sbomify.com/CVE-2024-5273/index.md)
```

## Sources

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

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