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 cacache

Dependencies

(20 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.10.01.13.0up to date
 digest^0.10.60.10.7up to date
 either^1.6.11.13.0up to date
 futures^0.3.170.3.31up to date
 hex^0.4.30.4.3up to date
 libc^0.2.1440.2.169up to date
 memmap2^0.5.80.9.5out of date
 miette^5.7.07.4.0out of date
 reflink-copy^0.1.90.1.20up to date
 serde^1.0.1301.0.216up to date
 serde_derive^1.0.1301.0.216up to date
 serde_json^1.0.681.0.134up to date
 sha1^0.10.50.10.6up to date
 sha2^0.10.60.10.8up to date
 ssri^9.0.09.2.0up to date
 tempfile^3.4.03.14.0up to date
 thiserror^1.0.402.0.9out of date
 tokio ⚠️^1.12.01.42.0maybe insecure
 tokio-stream^0.1.70.1.17up to date
 walkdir^2.3.22.5.0up to date

Dev dependencies

(4 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-attributes^1.1.21.1.2up to date
 criterion^0.4.00.5.1out of date
 lazy_static^1.4.01.5.0up to date
 tokio ⚠️^1.12.01.42.0maybe insecure

Security Vulnerabilities

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