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.
sccache(67 total, 15 outdated, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0 | 1.0.102 | up to date |
| ar | ^0.9 | 0.9.0 | up to date |
| async-trait | ^0.1 | 0.1.89 | up to date |
| backon | ^1 | 1.6.0 | up to date |
| base64 | ^0.21 | 0.22.1 | out of date |
| bincode | ^1 | 3.0.0 | out of date |
| blake3 | ^1 | 1.8.4 | up to date |
| byteorder | ^1.5 | 1.5.0 | up to date |
| bytes ⚠️ | ^1 | 1.11.1 | maybe insecure |
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| clap | ^4.5.13 | 4.6.0 | up to date |
| directories | ^6.0 | 6.0.0 | up to date |
| encoding_rs | ^0.8 | 0.8.35 | up to date |
| env_logger | ^0.11 | 0.11.10 | up to date |
| filetime | ^0.2 | 0.2.27 | up to date |
| flate2 | ^1.0 | 1.1.9 | up to date |
| fs-err | ^3 | 3.3.0 | up to date |
| futures | ^0.3 | 0.3.32 | up to date |
| gzp | ^2 | 2.0.2 | up to date |
| http | ^1.0 | 1.4.0 | up to date |
| http-body-util | ^0.1 | 0.1.3 | up to date |
| hyper | ^1.1 | 1.8.1 | up to date |
| hyper-util | ^0.1.3 | 0.1.20 | up to date |
| itertools | ^0.14 | 0.14.0 | up to date |
| jobserver | ^0.1 | 0.1.34 | up to date |
| jsonwebtoken | ^9 | 10.3.0 | out of date |
| libc | ^0.2.153 | 0.2.183 | up to date |
| linked-hash-map | ^0.5 | 0.5.6 | up to date |
| log | ^0.4 | 0.4.29 | up to date |
| memchr | ^2 | 2.8.0 | up to date |
| memmap2 | ^0.9.4 | 0.9.10 | up to date |
| mime | ^0.3 | 0.3.17 | up to date |
| number_prefix | ^0.4 | 0.4.0 | up to date |
| object | ^0.37 | 0.39.0 | out of date |
| opendal | ^0.55.0 | 0.55.0 | up to date |
| openssl | ^0.10.75 | 0.10.76 | up to date |
| rand | ^0.8.4 | 0.10.0 | out of date |
| regex | ^1.10.3 | 1.12.3 | up to date |
| reqsign | ^0.18.0 | 0.20.0 | out of date |
| reqwest | ^0.12 | 0.13.2 | out of date |
| semver | ^1.0 | 1.0.27 | up to date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_json | >=1.0, <1.0.147 | 1.0.149 | out of date |
| sha2 | ^0.10.8 | 0.11.0 | out of date |
| shlex | ^1.3.0 | 1.3.0 | up to date |
| strip-ansi-escapes | ^0.2 | 0.2.1 | up to date |
| tar ⚠️ | ^0.4.40 | 0.4.45 | maybe insecure |
| tempfile | ^3 | 3.27.0 | up to date |
| tokio ⚠️ | ^1 | 1.50.0 | maybe insecure |
| tokio-serde | ^0.9 | 0.9.0 | up to date |
| tokio-util | ^0.7 | 0.7.18 | up to date |
| toml | ^0.9 | 1.1.0+spec-1.1.0 | out of date |
| tower-service | ^0.3 | 0.3.3 | up to date |
| typed-path | ^0.12.0 | 0.12.3 | up to date |
| url | ^2 | 2.5.8 | up to date |
| uuid | ^1.9 | 1.23.0 | up to date |
| walkdir | ^2 | 2.5.0 | up to date |
| which | ^6 | 8.0.2 | out of date |
| zip | ^0.6 | 8.4.0 | out of date |
| zstd | ^0.13 | 0.13.3 | up to date |
| nix | ^0.30.0 | 0.31.2 | out of date |
| rouille | ^3.6 | 3.6.2 | up to date |
| syslog | ^7 | 7.0.0 | up to date |
| version-compare | ^0.1.1 | 0.2.1 | out of date |
| daemonix | ^0.1 | 0.1.0 | up to date |
| libmount | ^0.1.15 | 0.1.15 | up to date |
| windows-sys | ^0.52 | 0.61.2 | out of date |
(10 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| assert_cmd | ^2.0.13 | 2.2.0 | up to date |
| cc | ^1.0 | 1.2.58 | up to date |
| chrono | ^0.4.42 | 0.4.44 | up to date |
| codspeed-divan-compat | ^4 | 4.4.1 | up to date |
| filetime | ^0.2 | 0.2.27 | up to date |
| predicates | =3.1.0 | 3.1.4 | out of date |
| serial_test | ^3.1 | 3.4.0 | up to date |
| temp-env | ^0.3.6 | 0.3.6 | up to date |
| test-case | ^3.3.1 | 3.3.1 | up to date |
| thirtyfour | ^0.36 | 0.36.1 | up to date |
randomize_readdir(5 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ctor | ^0.2 | 0.8.0 | out of date |
| libc | ^0.2.99 | 0.2.183 | up to date |
| log | ^0.4 | 0.4.29 | up to date |
| rand | ^0.8 | 0.10.0 | out of date |
| simplelog | ^0.12 | 0.12.2 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
tokio: reject_remote_clients Configuration corruptionOn Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.
This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.
The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.
Ensure that pipe_mode is set first after initializing a ServerOptions. For example:
let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);
bytes: Integer overflow in `BytesMut::reserve`In the unique reclaim path of BytesMut::reserve, the condition
if v_capacity >= new_cap + offset
uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB.
This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.
use bytes::*;
fn main() {
let mut a = BytesMut::from(&b"hello world"[..]);
let mut b = a.split_off(5);
// Ensure b becomes the unique owner of the backing storage
drop(a);
// Trigger overflow in new_cap + offset inside reserve
b.reserve(usize::MAX - 6);
// This call relies on the corrupted cap and may cause UB & HBO
b.put_u8(b'h');
}
Users of BytesMut::reserve are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.
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.