hyper-staticfile's improper validation of Windows paths could lead to directory traversal attack
Priority LOW 38CWE-22Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
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.
Why it matters now
Fix Fixed hyper-staticfile (crates.io): 0.9.2, 0.10.0-alpha.2
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | hyper-staticfile (crates.io) | before 0.9.2 | 0.9.2 | Patch available | GHSA-7p7c-pvvx-2vx3 |
| — | hyper-staticfile (crates.io) | 0.10.0-alpha.1 to before 0.10.0-alpha.2 | 0.10.0-alpha.2 | Patch available | GHSA-7p7c-pvvx-2vx3 |
- hyper-staticfile (crates.io) Vendor— Affected before 0.9.2 Fixed in 0.9.2 Patch available GHSA-7p7c-pvvx-2vx3
- hyper-staticfile (crates.io) Vendor— Affected 0.10.0-alpha.1 to before 0.10.0-alpha.2 Fixed in 0.10.0-alpha.2 Patch available GHSA-7p7c-pvvx-2vx3
Remediation
- Fix · GHSA-7p7c-pvvx-2vx3 hyper-staticfile (crates.io) Fixed in 0.9.2 Advisory →
- Fix · GHSA-7p7c-pvvx-2vx3 hyper-staticfile (crates.io) Fixed in 0.10.0-alpha.2 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-7p7c-pvvx-2vx3
References
Other 5
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences