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 cached

Dependencies

(17 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.80.8.11up to date
 async-trait^0.10.1.83up to date
 cached_proc_macro^0.23.00.23.0up to date
 cached_proc_macro_types^0.1.10.1.1up to date
 directories^5.05.0.1up to date
 futures^0.30.3.31up to date
 hashbrown^0.140.15.0out of date
 once_cell^11.20.2up to date
 r2d2^0.80.8.10up to date
 redis^0.250.27.5out of date
 rmp-serde^1.11.3.0up to date
 serde^1.01.0.210up to date
 serde_json^1.01.0.131up to date
 sled^0.340.34.7up to date
 thiserror^11.0.64up to date
 tokio ⚠️^11.40.0maybe insecure
 web-time^1.1.01.1.0up to date

Dev dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 async-std^1.61.13.0up to date
 copy_dir^0.1.30.1.3up to date
 googletest^0.11.00.12.0out of date
 serial_test^33.1.1up to date
 smartstring^11.0.1up to date
 tempfile^3.10.13.13.0up to date

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