How severe is GHSA-7p7c-pvvx-2vx3?

No CVSS score has been assigned to GHSA-7p7c-pvvx-2vx3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7p7c-pvvx-2vx3?

GHSA-7p7c-pvvx-2vx3 affects the following packages: hyper-staticfile (crates.io), hyper-staticfile (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-7p7c-pvvx-2vx3?

Update hyper-staticfile to 0.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7p7c-pvvx-2vx3 is resolved across your whole dependency graph.

How do I detect GHSA-7p7c-pvvx-2vx3 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hyper-staticfile. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-7p7c-pvvx-2vx3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-7p7c-pvvx-2vx3?

O3 pinpoints whether GHSA-7p7c-pvvx-2vx3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7p7c-pvvx-2vx3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7p7c-pvvx-2vx3 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-7p7c-pvvx-2vx3 published, and has it been updated?

GHSA-7p7c-pvvx-2vx3 was published on December 5, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

GHSA-7p7c-pvvx-2vx3

hyper-staticfile's improper validation of Windows paths could lead to directory traversal attack

Also known asRUSTSEC-2022-0069

Published

Dec 5, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🦀hyper-staticfile🦀hyper-staticfile

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`hyper-staticfile`	all versions	0.9.2
🦀crates.io	`hyper-staticfile`	≥ 0.10.0-alpha.1&&< 0.10.0-alpha.2	0.10.0-alpha.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hyper-staticfile. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update hyper-staticfile to 0.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7p7c-pvvx-2vx3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-7p7c-pvvx-2vx3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7p7c-pvvx-2vx3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-7p7c-pvvx-2vx3 in your dependencies?

O3 detects GHSA-7p7c-pvvx-2vx3 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works