# GHSA-8v4j-7jgf-5rg9: Warp vulnerable to Path Traversal via Improper validation of Windows paths

> An attacker can read arbitrary files on Windows systems via path traversal in the Warp web framework's directory filter.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jan 2022
- **Also known as:** RUSTSEC-2022-0082

## What is GHSA-8v4j-7jgf-5rg9?

GHSA-8v4j-7jgf-5rg9 is a path traversal vulnerability in warp, published on 14 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

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

3 open source packages ship an affected version, including warp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `warp` | crates.io | All versions | 0.3.3 |
| `warp` | crates.io | All versions | 0.3.3 |
| `warp` | crates.io | From 0.0.0-0 | 0.3.3 |

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

Upgrade warp to 0.3.3 or later.

## Is GHSA-8v4j-7jgf-5rg9 being exploited?

There is no known exploitation of GHSA-8v4j-7jgf-5rg9 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8v4j-7jgf-5rg9 and fix it if it is affected.

What it is: GHSA-8v4j-7jgf-5rg9 is a path traversal vulnerability in warp, published on 14 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-8v4j-7jgf-5rg9 in the wild and no public exploit code.

Affected packages and fixed versions:
- warp (crates.io): affected all versions; fixed in 0.3.3
- warp (crates.io): affected all versions; fixed in 0.3.3
- warp (crates.io): affected from 0.0.0-0; fixed in 0.3.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-8v4j-7jgf-5rg9/ (Markdown: https://insights.sbomify.com/GHSA-8v4j-7jgf-5rg9/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8v4j-7jgf-5rg9

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8v4j-7jgf-5rg9/
Summaries are generated and may contain mistakes; the official description above is the record.