File disclosure via encoded static-path separator
Published Aug 1, 2022 · Updated Apr 22, 2025
Path traversal in Sanic before 20.12.7, 21.0.0 through 21.12.1, and 22.0.0 through 22.6.0 allows remote attackers to read lateral files. The app.static handler checks the quoted path for ../ before URL decoding, so ..%2F introduces a separator after that traversal check. Exploitation requires a static-directory route and a known or guessed lateral path; the resolved-path prefix check still blocks escape to parent directories.
Summary
What happened
Path traversal in Sanic before 20.12.7, 21.0.0 through 21.12.1, and 22.0.0 through 22.6.0 allows remote attackers to read lateral files. The app.static handler checks the quoted path for ../ before URL decoding, so ..%2F introduces a separator after that traversal check. Exploitation requires a static-directory route and a known or guessed lateral path; the resolved-path prefix check still blocks escape to parent directories.
The record
- CVE
- CVE-2022-35920
- Published
- Aug 1, 2022
- Updated
- Apr 22, 2025
- Vendor
- Sanic Community Organization
- Product
- Sanic
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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=< 20.12.7
- Affected versionversion=>= 21.0.0, < 21.12.2
- Affected versionversion=>= 22.0.0, < 22.6.1
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
- Encoded-slash static traversal reproductionproof 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