Rust advisories / hyper-staticfile
Vulnerability MediumRUSTSEC-2022-0069 · hyper-staticfile
RUSTSEC-2022-0069: Improper validation of Windows paths could lead to directory traversal attack
Short answerA security vulnerability in the hyper-staticfile crate: Improper validation of Windows paths could lead to directory traversal attack. GitHub rates it Medium. Fixed in 0.10.0-alpha.2, 0.9.2: update to a fixed version.
| Crate | hyper-staticfile |
|---|---|
| Type | Vulnerability (file-disclosure) |
| Affected versions | Before 0.9.2; from 0.10.0 before 0.10.0-alpha.2. |
| Fixed in | 0.10.0-alpha.2, 0.9.2 |
| Severity | Medium (GitHub rating) |
| Published | 2022-11-30 |
| Last changed | 2023-11-08 |
| Also known as | GHSA-7p7c-pvvx-2vx3 |
What to do
- See which version you have:
cargo tree -i hyper-staticfile(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p hyper-staticfile. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplehyper-staticfile = "0.9.2") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Path resolution in hyper-staticfile didn't correctly validate Windows paths meaning paths like /foo/bar/c:/windows/web/screen/img101.png would be allowed and respond with the contents of c:/windows/web/screen/img101.png. Thus users could potentially read files anywhere on the filesystem.
This only impacts Windows. Linux and other unix likes are not impacted by this.
References
- Package: crates.io/crates/hyper-staticfile
- Advisory: rustsec.org/advisories/RUSTSEC-2022-0069.html
- Report: github.com/stephank/hyper-staticfile/issues/35
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for hyper-staticfile
Up next
Same cratehyper-staticfile: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?