Description
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.
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| crates.io | hyper-staticfile | < 0.9.2 | 0.9.2 | GHSA-7p7c-pvvx-2vx3 |
| crates.io | hyper-staticfile | >= 0.10.0-alpha.1, < 0.10.0-alpha.2 | 0.10.0-alpha.2 | GHSA-7p7c-pvvx-2vx3 |
| crates.io | hyper-staticfile | >= 0.0.0-0, < 0.9.2 · >= 0.10.0-0, < 0.10.0-alpha.2 | 0.9.2, 0.10.0-alpha.2 | RUSTSEC-2022-0069 |
References
- https://github.com/stephank/hyper-staticfile/issues/35 web
- https://github.com/stephank/hyper-staticfile/pull/36 web
- https://github.com/stephank/hyper-staticfile/commit/1e40e31d64bc6b32e595d24074092dcf84410b2b web
- https://github.com/stephank/hyper-staticfile package
- https://rustsec.org/advisories/RUSTSEC-2022-0069.html web