Arbitrary file read via inverted path check
Published Feb 22, 2024 · Updated Aug 21, 2024
Path traversal in Appwrite 0.5.0 through 0.12.x before 0.12.2 allows remote attackers to read arbitrary local files without authentication. The ACME-challenge handler builds a real path from the request URI, then applies logical negation before comparing its prefix with the certificate-storage base, so traversal paths pass the containment check. Exploitation requires the .well-known/acme-challenge directory under APP_STORAGE_CERTIFICATES, which Appwrite creates when Let's Encrypt certificates are installed.
Summary
What happened
Path traversal in Appwrite 0.5.0 through 0.12.x before 0.12.2 allows remote attackers to read arbitrary local files without authentication. The ACME-challenge handler builds a real path from the request URI, then applies logical negation before comparing its prefix with the certificate-storage base, so traversal paths pass the containment check. Exploitation requires the .well-known/acme-challenge directory under APP_STORAGE_CERTIFICATES, which Appwrite creates when Let's Encrypt certificates are installed.
The record
- CVE
- CVE-2022-25377
- Published
- Feb 22, 2024
- Updated
- Aug 21, 2024
- Vendor
- Appwrite
- Product
- Appwrite
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 2024CVE publishedPublication date reported by the CVE source.
- Aug 21, 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=0.5.0 <0.12.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
- Unauthenticated LFI proof of conceptproof 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