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 sccache

Dependencies

(64 total, 9 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.82up to date
 ar^0.90.9.0up to date
 async-trait^0.10.1.80up to date
 base64^0.210.22.0out of date
 bincode^11.3.3up to date
 blake3^11.5.1up to date
 byteorder^1.51.5.0up to date
 bytes^11.6.0up to date
 chrono ⚠️^0.40.4.38maybe insecure
 clap^4.4.184.5.4up to date
 directories^5.0.15.0.1up to date
 encoding_rs^0.80.8.34up to date
 env_logger^0.100.11.3out of date
 filetime^0.20.2.23up to date
 flate2^1.01.0.28up to date
 fs-err^2.112.11.0up to date
 futures^0.30.3.30up to date
 gzp^0.11.30.11.3up to date
 http^1.01.1.0up to date
 http-body-util^0.10.1.1up to date
 hyper^1.11.3.1up to date
 hyper-util^0.1.30.1.3up to date
 is-terminal^0.4.120.4.12up to date
 jobserver^0.10.1.31up to date
 jsonwebtoken^99.3.0up to date
 libc^0.2.1530.2.153up to date
 linked-hash-map^0.50.5.6up to date
 log^0.40.4.21up to date
 memchr^22.7.2up to date
 mime^0.30.3.17up to date
 num_cpus^1.161.16.0up to date
 number_prefix^0.40.4.0up to date
 once_cell^1.191.19.0up to date
 opendal^0.45.10.45.1up to date
 openssl^0.10.640.10.64up to date
 rand^0.8.40.8.5up to date
 regex^1.10.31.10.4up to date
 reqsign^0.14.70.15.0out of date
 reqwest^0.110.12.4out of date
 retry^22.0.0up to date
 semver^1.01.0.22up to date
 serde^1.01.0.198up to date
 serde_json^1.01.0.116up to date
 sha2^0.10.80.10.8up to date
 strip-ansi-escapes^0.20.2.0up to date
 tar^0.4.400.4.40up to date
 tempfile^33.10.1up to date
 tokio ⚠️^11.37.0maybe insecure
 tokio-serde^0.80.9.0out of date
 tokio-util^0.70.7.10up to date
 toml^0.80.8.12up to date
 tower^0.40.4.13up to date
 url^22.5.0up to date
 uuid^1.71.8.0up to date
 walkdir^22.5.0up to date
 which^66.0.1up to date
 zip^0.61.1.1out of date
 zstd^0.130.13.1up to date
 memmap2^0.9.40.9.4up to date
 nix^0.27.10.28.0out of date
 object^0.320.35.0out of date
 rouille^3.63.6.2up to date
 syslog^66.1.1up to date
 version-compare^0.1.10.2.0out of date

Dev dependencies

(10 total, 1 outdated)

CrateRequiredLatestStatus
 assert_cmd^2.0.132.0.14up to date
 cc^1.01.0.95up to date
 chrono^0.4.330.4.38up to date
 filetime^0.20.2.23up to date
 itertools^0.120.12.1up to date
 predicates=3.1.03.1.0up to date
 serial_test^2.03.1.0out of date
 temp-env^0.3.60.3.6up to date
 test-case^3.3.13.3.1up to date
 thirtyfour_sync^0.270.27.1up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On 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.

Workarounds

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);