Reposilite vulnerable to path traversal while serving javadoc expanded files (arbitrary file read) (GHSL-2024-074)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary Reposilite v3.5.10 is affected by an Arbitrary File Read vulnerability via path traversal while serving expanded javadoc files. Details The problem lies in the way how the expanded javadoc files are served. The GET /javadoc/{repository}/<gav/raw/<resource route uses the <resource path parameter to find the file in the javadocUnpackPath directory and returns it's content to the user. JavadocFacade.kt#L77: In this case, the <resource path parameter can contain path traversal characters such as /../../. Since the path is concatenated with the main directory, it opens the possibility to read files outside the javadocUnpackPath directory. Impact This issue may lead to Arbitrary File Read on the server. A potential attacker can read some sensitive file, such as reposilite.db, that contains the sqlite database used by Reposilite. This database contains the sensitive information used by Reposilite, including passwords and hashes of issued tokens. Also, the configuration.cdn file can…

Published by the source

4 Nov 2024, 23:23 UTC

Last modified by the source

4 Nov 2024, 23:23 UTC

Source last checked

26 Oct 2026, 16:31 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-82j3-hf72-7x93

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-82j3-hf72-7x93

Advisory: Reposilite vulnerable to path traversal while serving javadoc expanded files (arbitrary file read) (`GHSL-2024-074`)
IDs: GHSA-82j3-hf72-7x93
Record: https://patchnext.com/advisories/ghsa-82j3-hf72-7x93 (revision 1, source checked 26 Oct 2026, 16:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.reposilite:reposilite-backend 3.5.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.reposilite:reposilite-backend: affected >= 3.3.0, < 3.5.12; fixed in 3.5.12

## Suggested inspection (read-only)
- Maven com.reposilite:reposilite-backend: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.reposilite:reposilite-backend.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-82j3-hf72-7x93 (GitHub-reviewed advisory GHSA-82j3-hf72-7x93 lists affected ranges: Maven com.reposilite:reposilite-backend >=3.3.0 <3.5.12)

Commands are suggestions: review each one before running it.