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 redis-async

Dependencies

(13 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.01.9.0up to date
 futures-channel^0.3.70.3.31up to date
 futures-sink^0.3.70.3.31up to date
 futures-util^0.3.70.3.31up to date
 log^0.4.110.4.22up to date
 native-tls^0.20.2.12up to date
 pin-project^1.01.1.7up to date
 socket2^0.50.5.8up to date
 tokio ⚠️^1.01.42.0maybe insecure
 tokio-native-tls^0.3.00.3.1up to date
 tokio-rustls^0.260.26.1up to date
 tokio-util^0.70.7.13up to date
 webpki-roots^0.260.26.7up to date

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.110.11.5up to date
 futures^0.3.70.3.31up to date
 tokio ⚠️^1.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);