How severe is GHSA-5wvv-q5fv-2388?

No CVSS score has been assigned to GHSA-5wvv-q5fv-2388 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5wvv-q5fv-2388?

GHSA-5wvv-q5fv-2388 affects the following packages: hyper-staticfile (crates.io), hyper-staticfile (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-5wvv-q5fv-2388?

Update hyper-staticfile to 0.9.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5wvv-q5fv-2388 is resolved across your whole dependency graph.

How do I detect GHSA-5wvv-q5fv-2388 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-5wvv-q5fv-2388 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-5wvv-q5fv-2388?

O3 pinpoints whether GHSA-5wvv-q5fv-2388 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-5wvv-q5fv-2388 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5wvv-q5fv-2388 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-5wvv-q5fv-2388 published, and has it been updated?

GHSA-5wvv-q5fv-2388 was published on December 30, 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-5wvv-q5fv-2388

hyper-staticfile's location header incorporates user input, allowing open redirect

Also known asRUSTSEC-2022-0072

Published

Dec 30, 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

When hyper-staticfile performs a redirect for a directory request (e.g. a request for /dir that redirects to /dir/), the Location header value was derived from user input (the request path), simply appending a slash. The intent was to perform an origin-relative redirect, but specific inputs allowed performing a scheme-relative redirect instead.

An attacker could craft a special URL that would appear to be for the correct domain, but immediately redirects to a malicious domain. Such a URL can benefit phishing attacks, for example an innocent looking link in an email.

Affected Packages

2 total 2 fixed

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

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.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5wvv-q5fv-2388 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-5wvv-q5fv-2388 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-5wvv-q5fv-2388. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

When `hyper-staticfile` performs a redirect for a directory request (e.g. a request for `/dir` that redirects to `/dir/`), the `Location` header value was derived from user input (the request path), simply appending a slash. The intent was to perform an origin-relative redirect, but specific inputs allowed performing a scheme-relative redirect instead. An attacker could craft a special URL that would appear to be for the correct domain, but immediately redirects to a malicious domain. Such a URL can benefit phishing attacks, for example an innocent looking link in an email.

O3 Security · Impact-Aware SCA

Is GHSA-5wvv-q5fv-2388 in your dependencies?

O3 detects GHSA-5wvv-q5fv-2388 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