# CVE-2024-36117: Path traversal while serving Reposilite javadoc expanded files

> Attackers can read arbitrary files from the server via path traversal in Reposilite's javadoc serving feature.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2024
- **Updated:** 4 Nov 2024
- **Also known as:** GHSA-82j3-hf72-7x93

## What is CVE-2024-36117?

CVE-2024-36117 is a high-severity path traversal vulnerability in dzikoysk reposilite, published on 19 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Reposilite is an open source, lightweight and easy-to-use repository manager for Maven based artifacts in JVM ecosystem. Reposilite v3.5.10 is affected by an Arbitrary File Read vulnerability via path traversal while serving expanded javadoc files. Reposilite has addressed this issue in version 3.5.12. There are no known workarounds for this vulnerability. This issue was discovered and reported by the GitHub Security lab and is also tracked as GHSL-2024-074.

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

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

2 open source packages ship an affected version, including com.reposilite:reposilite-backend. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.reposilite:reposilite-backend` | Maven | From 3.3.0 | 3.5.12 |
| `com.reposilite:reposilite-backend` | Maven | From 3.3.0 | 3.5.12 |

Products: Reposilite Reposilite.

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

Upgrade com.reposilite:reposilite-backend to 3.5.12 or later.

## Is CVE-2024-36117 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36117 exists.

Public exploit code:

- Reposilite >= 3.3.0, < 3.5.12 - Arbitrary File Read (nuclei): http/cves/2024/CVE-2024-36117.yaml

## Other vulnerabilities in dzikoysk reposilite

- [CVE-2024-36116](https://insights.sbomify.com/CVE-2024-36116/): Path traversal in Reposilite javadoc file expansion (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36117 is a high-severity path traversal vulnerability in dzikoysk reposilite, published on 19 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36117 exists.

Affected packages and fixed versions:
- com.reposilite:reposilite-backend (Maven): affected from 3.3.0; fixed in 3.5.12
- com.reposilite:reposilite-backend (Maven): affected from 3.3.0; fixed in 3.5.12

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

## Sources

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

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