Unauthenticated file disclosure via .cpr path traversal
Published Jul 14, 2023 · Updated Feb 13, 2025
Path traversal in copyparty before 1.8.2 allows remote attackers to read process-accessible files through crafted /.cpr/ requests. The HTTP GET handler joined the untrusted path suffix to its web directory and sent the result without canonicalizing it or enforcing containment. Exploitation requires no authentication but requires the target file's absolute or installation-relative path; directory listing is unavailable, and OS permissions bound disclosure.
Summary
What happened
Path traversal in copyparty before 1.8.2 allows remote attackers to read process-accessible files through crafted /.cpr/ requests. The HTTP GET handler joined the untrusted path suffix to its web directory and sent the result without canonicalizing it or enforcing containment. Exploitation requires no authentication but requires the target file's absolute or installation-relative path; directory listing is unavailable, and OS permissions bound disclosure.
The record
- CVE
- CVE-2023-37474
- Published
- Jul 14, 2023
- Updated
- Feb 13, 2025
- Vendor
- copyparty
- Product
- copyparty
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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 <1.8.2
- Affected versionversion=< 1.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 .cpr path traversal request 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