Unauthenticated file disclosure via uncleaned request paths
Published Dec 27, 2022 · Updated Apr 11, 2025
Path traversal in aah before 0.12.4 allows remote attackers to read server-accessible files through crafted static-file requests. HTTPEngine.Handle forwarded the request URL path into static-file routing without first canonicalizing dot segments, so traversal sequences escaped the configured target directory. The application must expose a static-file route, and disclosure is limited to files readable by the server process.
Summary
What happened
Path traversal in aah before 0.12.4 allows remote attackers to read server-accessible files through crafted static-file requests. HTTPEngine.Handle forwarded the request URL path into static-file routing without first canonicalizing dot segments, so traversal sequences escaped the configured target directory. The application must expose a static-file route, and disclosure is limited to files readable by the server process.
The record
- CVE
- CVE-2020-36559
- Published
- Dec 27, 2022
- Updated
- Apr 11, 2025
- Vendor
- aah
- Product
- aah
- Classifications
- CWE-22, T1190, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 27, 2022CVE publishedPublication date reported by the CVE source.
- Apr 11, 2025Record 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=0 <0.12.4
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
No public exploit references are available in this record.
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