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.
toast(19 total, 10 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| atty | ^0.2 | 0.2.14 | up to date |
| clap | ^2 | 4.6.0 | out of date |
| colored | ^1 | 3.1.1 | out of date |
| crossbeam | ^0.7 | 0.8.4 | out of date |
| ctrlc | ^3 | 3.5.2 | up to date |
| dirs | ^1 | 6.0.0 | out of date |
| env_logger | ^0.6 | 0.11.10 | out of date |
| hex | ^0.3 | 0.4.3 | out of date |
| indicatif | ^0.11 | 0.18.4 | out of date |
| lazy_static | ^1.3 | 1.5.0 | up to date |
| log | ^0.4 | 0.4.29 | up to date |
| scopeguard | ^1 | 1.2.0 | up to date |
| serde | ^1 | 1.0.228 | up to date |
| serde_yaml ⚠️ | ^0.8 | 0.9.34+deprecated | out of date |
| sha2 | ^0.8 | 0.11.0 | out of date |
| tar ⚠️ | ^0.4 | 0.4.45 | maybe insecure |
| tempfile | ^3 | 3.27.0 | up to date |
| uuid | ^0.7 | 1.23.0 | out of date |
| walkdir | ^2 | 2.5.0 | up to date |
serde_yaml: Uncontrolled recursion leads to abort in deserializationAffected versions of this crate did not properly check for recursion while deserializing aliases.
This allows an attacker to make a YAML file with an alias referring to itself causing an abort.
The flaw was corrected by checking the recursion depth.
tar: `unpack_in` can chmod arbitrary directories by following symlinksIn 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 nonzeroVersions 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.