Arbitrary file read via unsanitized Javadoc resource path
Published Jun 19, 2024 · Updated Nov 4, 2024
Path traversal in Reposilite 3.3.0 through 3.5.11 allows remote attackers to read arbitrary server files through Javadoc requests. The findRawJavadocResource method resolves the untrusted resource string against javadocUnpackPath without removing traversal segments. No authentication or user interaction is required, but a hosted Javadoc archive must be available; exposed files can include the repository database and configuration secrets.
Summary
What happened
Path traversal in Reposilite 3.3.0 through 3.5.11 allows remote attackers to read arbitrary server files through Javadoc requests. The findRawJavadocResource method resolves the untrusted resource string against javadocUnpackPath without removing traversal segments. No authentication or user interaction is required, but a hosted Javadoc archive must be available; exposed files can include the repository database and configuration secrets.
The record
- CVE
- CVE-2024-36117
- Published
- Jun 19, 2024
- Updated
- Nov 4, 2024
- Vendor
- dzikoysk
- Product
- Reposilite
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 19, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.3.0, < 3.5.12
- Affected versionversion=3.3.0 <3.5.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory Javadoc traversal reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo