How severe is GHSA-qrqq-9c63-xfrg?

No CVSS score has been assigned to GHSA-qrqq-9c63-xfrg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qrqq-9c63-xfrg?

GHSA-qrqq-9c63-xfrg affects the following packages: tower-http (crates.io), tower-http (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-qrqq-9c63-xfrg?

Update tower-http to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qrqq-9c63-xfrg is resolved across your whole dependency graph.

How do I detect GHSA-qrqq-9c63-xfrg in my crates.io dependencies?

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

How do I mitigate GHSA-qrqq-9c63-xfrg 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-qrqq-9c63-xfrg?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qrqq-9c63-xfrg can be triaged on real exposure rather than presence alone.

Is GHSA-qrqq-9c63-xfrg actively exploited in the wild?

No public exploit code has been indexed for GHSA-qrqq-9c63-xfrg 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-qrqq-9c63-xfrg published, and has it been updated?

GHSA-qrqq-9c63-xfrg was published on August 11, 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

Not in CISA KEV

GHSA-qrqq-9c63-xfrg — tower-http

Fix: tower-rs/tower-http#204

GHSA-qrqq-9c63-xfrg is a security vulnerability in tower-http. A fix is available for tower-http — see the affected versions and patch details below.

tower-http's improper validation of Windows paths could lead to directory traversal attack

Also known asRUSTSEC-2022-0043

Published

Aug 11, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Real-World Exposure

2 pkgs affected

🦀tower-http🦀tower-http

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

tower_http::services::fs::ServeDir 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.

See tower-http#204 for more details.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`tower-http`	≥ 0.2.0&&< 0.2.1	0.2.1`cargo update -p tower-http --precise 0.2.1`
🦀crates.io	`tower-http`	all versions	0.1.3`cargo update -p tower-http --precise 0.1.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tower-http, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tower-http to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qrqq-9c63-xfrg 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-qrqq-9c63-xfrg can be triaged on real exposure rather than presence alone.

Tailored to GHSA-qrqq-9c63-xfrg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`tower_http::services::fs::ServeDir` 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. See [tower-http#204] for more details. [tower-http#204]: https://github.com/tower-rs/tower-http/pull/204

O3 Security · Impact-Aware SCA

Is GHSA-qrqq-9c63-xfrg in your dependencies?

O3 Security finds GHSA-qrqq-9c63-xfrg 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