File disclosure via post-decoding path traversal
Published Jan 4, 2024 · Updated Jul 14, 2026
Path traversal in iodine before 0.7.33 allows remote attackers to read files outside the static server's public folder via malicious URLs. The http_sendfile2 path check examines traversal markers before percent-decoding, so encoded slash and dot segments become unchecked filesystem paths after decoding. The unauthenticated read is reachable only when an application enables iodine's native static-file service; disclosure is limited to files readable by the server process.
Summary
What happened
Path traversal in iodine before 0.7.33 allows remote attackers to read files outside the static server's public folder via malicious URLs. The http_sendfile2 path check examines traversal markers before percent-decoding, so encoded slash and dot segments become unchecked filesystem paths after decoding. The unauthenticated read is reachable only when an application enables iodine's native static-file service; disclosure is limited to files readable by the server process.
The record
- CVE
- CVE-2024-22050
- Published
- Jan 4, 2024
- Updated
- Jul 14, 2026
- Vendor
- Boaz Segev
- Product
- iodine
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 4, 2024CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record 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.7.33
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
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