How severe is GHSA-8v4j-7jgf-5rg9?

No CVSS score has been assigned to GHSA-8v4j-7jgf-5rg9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8v4j-7jgf-5rg9?

GHSA-8v4j-7jgf-5rg9 affects the following packages: warp (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-8v4j-7jgf-5rg9?

Update warp to 0.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8v4j-7jgf-5rg9 is resolved across your whole dependency graph.

How do I detect GHSA-8v4j-7jgf-5rg9 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for warp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-8v4j-7jgf-5rg9 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-8v4j-7jgf-5rg9?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8v4j-7jgf-5rg9 can be triaged on real exposure rather than presence alone.

Is GHSA-8v4j-7jgf-5rg9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8v4j-7jgf-5rg9 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-8v4j-7jgf-5rg9 published, and has it been updated?

GHSA-8v4j-7jgf-5rg9 was published on January 31, 2023 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

Not in CISA KEV

GHSA-8v4j-7jgf-5rg9 — warp

Fix: seanmonstar/warp#997

GHSA-8v4j-7jgf-5rg9 is a security vulnerability in warp. A fix is available for warp — see the affected versions and patch details below.

Warp vulnerable to Path Traversal via Improper validation of Windows paths

Also known asRUSTSEC-2022-0082

Published

Jan 31, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀warp

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 warp::filters::fs::dir 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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`warp`	all versions	0.3.3`cargo update -p warp --precise 0.3.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for warp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update warp to 0.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8v4j-7jgf-5rg9 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8v4j-7jgf-5rg9 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-8v4j-7jgf-5rg9. 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 `warp::filters::fs::dir` 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-8v4j-7jgf-5rg9 in your dependencies?

O3 Security finds GHSA-8v4j-7jgf-5rg9 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works