Deps.rs

matthiaskrgr / cargo-cache

[![dependency status](https://deps.rs/repo/github/matthiaskrgr/cargo-cache/status.svg)](https://deps.rs/repo/github/matthiaskrgr/cargo-cache)

This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate cargo-cache

Dependencies

(16 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 cargo_metadata^0.15.20.23.1out of date
 cfg-if^1.0.01.0.4up to date
 chrono^0.4.230.4.45up to date
 clap^3.0.04.6.7out of date
 dirs-next^2.0.02.0.0up to date
 flate2^1.0.251.1.10up to date
 git2^0.160.21.0out of date
 home^0.5.40.5.12up to date
 humansize^2.1.02.1.3up to date
 rayon^1.6.11.12.0up to date
 regex^1.7.11.13.1up to date
 remove_dir_all^0.8.21.0.0out of date
 rustc_tools_util=0.2.00.4.2out of date
 tar ⚠️^0.4.380.4.46maybe insecure
 unicode-normalization^0.1.220.1.25up to date
 walkdir^2.3.22.5.0up to date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 path-slash^0.2.10.2.1up to date
 pretty_assertions^1.3.01.4.1up to date
 fs_extra^1.2.01.3.0up to date
 tempfile^3.4.03.27.0up to date

Build dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 rustc_tools_util=0.2.00.4.2out of date

Security Vulnerabilities

tar: `unpack_in` can chmod arbitrary directories by following symlinks

RUSTSEC-2026-0067

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() 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.

tar: tar-rs incorrectly ignores PAX size headers if header size is nonzero

RUSTSEC-2026-0068

Versions 0.4.44 and below of tar-rs have conditional logic that skips the PAX size header in cases where the base header size is nonzero.

As part of CVE-2025-62518, the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header. This is almost the inverse of the astral-tokio-tar issue.

Any discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers. In this case, the tar-rs (Rust tar) crate is an outlier in checking for the header size — other tar parsers (including e.g. Go archive/tar) unconditionally use the PAX size override. This can affect anything that uses the tar crate to parse archives and expects to have a consistent view with other parsers.

This issue has been fixed in version 0.4.45.