Deps.rs

igankevich / wolfpack

[![dependency status](https://deps.rs/repo/github/igankevich/wolfpack/status.svg)](https://deps.rs/repo/github/igankevich/wolfpack)

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 wolfpack

Dependencies

(66 total, 11 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ar^0.9.00.9.0up to date
 async-trait^0.1.890.1.89up to date
 base16ct^1.0.01.0.0up to date
 base58^0.2.00.2.0up to date
 base64ct^1.8.31.8.3up to date
 bitflags^2.10.02.11.0up to date
 blake2b_simd^1.0.41.0.4up to date
 bzip2^0.6.10.6.1up to date
 chrono^0.4.430.4.44up to date
 clap^4.5.544.6.0up to date
 command-error^0.8.00.8.0up to date
 constant_time_eq^0.4.20.4.2up to date
 kpea^0.2.50.3.0out of date
 crc^3.4.03.4.0up to date
 deko^0.6.00.6.0up to date
 der^0.7.100.8.0out of date
 ed25519-dalek^2.2.02.2.0up to date
 elb^0.4.00.4.0up to date
 elb-dl^0.4.00.4.0up to date
 flate2^1.1.81.1.9up to date
 fs-err^3.2.23.3.0up to date
 futures^0.3.310.3.32up to date
 futures-util^0.3.310.3.32up to date
 hex^0.4.30.4.3up to date
 hkdf^0.12.40.12.4up to date
 indicatif^0.18.30.18.4up to date
 ksign^0.4.00.4.0up to date
 libc^0.2.1800.2.183up to date
 log^0.4.290.4.29up to date
 md5^0.8.00.8.0up to date
 normalize-path^0.2.10.2.1up to date
 page_size^0.6.00.6.0up to date
 parking_lot^0.12.50.12.5up to date
 pgp^0.15.00.19.0out of date
 pkcs8^0.10.20.10.2up to date
 quick-xml^0.39.00.39.2up to date
 rand^0.8.50.10.0out of date
 rand_chacha^0.3.10.10.0out of date
 rand_mt^4.2.26.0.2out of date
 reqwest^0.13.10.13.2up to date
 rusqlite^0.38.00.39.0out of date
 rusqlite_migration^2.4.02.5.0up to date
 secp256k1^0.30.00.31.1out of date
 serde^1.0.2281.0.228up to date
 serde_json^1.0.1491.0.149up to date
 sha1^0.10.60.10.6up to date
 sha2^0.10.90.11.0out of date
 similar-asserts^1.7.01.7.0up to date
 spki^0.7.30.7.3up to date
 sql_minifier^0.1.70.1.7up to date
 static_assertions^1.1.01.1.0up to date
 stuckliste^0.4.00.4.0up to date
 tantivy^0.25.00.25.0up to date
 tar ⚠️^0.4.440.4.45maybe insecure
 tempfile^3.24.03.27.0up to date
 thiserror^2.0.182.0.18up to date
 threadpool^1.8.11.8.1up to date
 tokio^1.49.01.50.0up to date
 toml^0.9.111.1.0+spec-1.1.0out of date
 uname-rs^0.1.10.1.1up to date
 walkdir^2.5.02.5.0up to date
 liblzma^0.4.50.4.6up to date
 zar^0.2.00.2.0up to date
 zeroize^1.8.21.8.2up to date
 zip^6.0.08.4.0out of date
 zstd^0.13.30.13.3up to date

Dev dependencies

(5 total, all up-to-date)

CrateRequiredLatestStatus
 arbitrary^1.4.21.4.2up to date
 arbtest^0.3.20.3.2up to date
 gcollections^1.5.01.6.0up to date
 intervallum^1.4.41.4.4up to date
 pretty-hex^0.4.10.4.2up to 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.