GHSA-xx64-wwv2-hcqq — astral-tokio-tar
GHSA-xx64-wwv2-hcqq is a security vulnerability in astral-tokio-tar. A fix is available for astral-tokio-tar — see the affected versions and patch details below.
astral-tokio-tar: `unpack_in` can chmod arbitrary directories by following symlinks
Real-World Exposure
astral-tokio-tarReal-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
Impact
In versions 0.6.0 and earlier of astral-tokio-tar, the unpack_in API could inadvertently modify the permissions of external (i.e. non-archive) directories outside of the archive. An attacker could use this to contrite a tar archive that maliciously changes directory permissions outside of its intended hierarchy. This flaw only affects directories; individual file permissions cannot be modified via it.
See GHSA-j4xf-2g29-59ph for the equivalent flaw in the tar crate.
Patches
Versions 0.6.1 and newer of astral-tokio-tar use fs::symlink_metdata rather than fs::metadata, avoiding the traversal.
Workarounds
Users are advised to upgrade to version 0.6.1 or newer to address this advisory.
Users should experience no breaking changes as a result of the patch above.
Resources
- GHSA-j4xf-2g29-59ph for the original
tarvulnerability
Attribution
- Reporter: Adam Harvey (@lawngnome)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | astral-tokio-tar | all versions | 0.6.1cargo update -p astral-tokio-tar --precise 0.6.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for astral-tokio-tar, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update astral-tokio-tar to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xx64-wwv2-hcqq 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-xx64-wwv2-hcqq can be triaged on real exposure rather than presence alone.
Tailored to GHSA-xx64-wwv2-hcqq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-xx64-wwv2-hcqq in your dependencies?
O3 Security finds GHSA-xx64-wwv2-hcqq across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.