tar
Affected
- introduced
0.0.0-0, fixed0.4.45(semver)
Fixed versions
0.4.45
Fix
- Fixed version
0.4.45cargo update -p tar --precise 0.4.45
Advisory
Also known as: CVE-2026-33056, GHSA-j4xf-2g29-59ph
unpack_in can chmod arbitrary directories by following symlinks
In versions 0.4.44 and below of tar-rs, when unpacking a tar archive, the tar
crate's unpack_dir function uses [fs::metadata()][fs-metadata] to check
whether a path that already exists is a directory. Because fs::metadata()
follows symbolic links, a crafted tarball containing a symlink entry followed
by a directory entry with the same name causes the crate to treat the symlink
target as a valid existing directory — and subsequently apply chmod to it. This
allows an attacker to modify the permissions of arbitrary directories outside
the extraction root.
This issue has been fixed in version 0.4.45.
[fs-metadata]: https://doc.rust-lang.org/std/fs/fn.metadata.html
Not rated by the source.
0.0.0-0, fixed 0.4.45 (semver)0.4.45
0.4.45cargo update -p tar --precise 0.4.45Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0