GitHub Advisoryadvisory · crates.io

GHSA-7p7c-pvvx-2vx3 hyper-staticfile's improper validation of Windows paths could lead to directory traversal attack

MEDIUM Published 2022-12-05 Modified 2022-12-05 Official page ↗
Ecosystem
crates.io
Packages
hyper-staticfile
Severity
Moderate
Weaknesses
CWE-22
Reviewed
2022-12-05

Affected packages

• crates.io hyper-staticfile: < 0.9.2 → fixed in 0.9.2 • crates.io hyper-staticfile: >= 0.10.0-alpha.1, < 0.10.0-alpha.2 → fixed in 0.10.0-alpha.2

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.

Related

Weakness · CWE (1)

  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory weakness

References