Classpath disclosure via asset path traversal
Published May 11, 2020 · Updated Aug 4, 2024
Path traversal in Jooby before 1.6.7 and 2.0.0 through 2.8.1 allows remote attackers to read sensitive classpath resources. AssetHandler resolves unmatched file-system asset requests through the class loader without confining the normalized resource name to the configured route prefix. Unauthenticated HTTP access to an application exposing Jooby asset routes is enough to retrieve configuration or application class files.
Summary
What happened
Path traversal in Jooby before 1.6.7 and 2.0.0 through 2.8.1 allows remote attackers to read sensitive classpath resources. AssetHandler resolves unmatched file-system asset requests through the class loader without confining the normalized resource name to the configured route prefix. Unauthenticated HTTP access to an application exposing Jooby asset routes is enough to retrieve configuration or application class files.
The record
- CVE
- CVE-2020-7647
- Published
- May 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jooby Project
- Product
- Jooby
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 2020CVE publishedPublication date reported by the CVE source.
- Aug 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=all versions before 1.6.7 and all versions after 2.0.0 inclusive and before 2.8.2
What conditions does exploitation require?
What is affected?
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
- Upstream crafted asset-path examplesproof 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