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 kash

Dependencies

(13 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.83up to date
 directories^5.05.0.1up to date
 instant^0.10.1.13up to date
 kash_macros^0.50.4.0out of date
 moka^0.120.12.8up to date
 once_cell^11.20.2up to date
 r2d2^0.80.8.10up to date
 redis^0.270.27.5up to date
 rmp-serde^1.11.3.0up to date
 serde^1.01.0.215up to date
 sled^0.340.34.7up to date
 thiserror^12.0.3out of date
 tokio ⚠️^11.41.1maybe insecure

Dev dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 copy_dir^0.10.1.3up to date
 googletest^0.120.12.0up to date
 serial_test^33.2.0up to date
 smartstring^11.0.1up to date
 tempfile^33.14.0up to date
 tokio ⚠️^11.41.1maybe 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);