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

Dependencies

(21 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arc-swap^1.1.01.7.1up to date
 async-native-tls^0.30.5.0out of date
 async-std^1.5.01.13.0up to date
 async-trait^0.1.240.1.83up to date
 bytes^11.8.0up to date
 combine^4.64.6.7up to date
 crc16^0.40.4.0up to date
 dtoa^0.41.0.9out of date
 futures^0.3.30.3.31up to date
 futures-util^0.3.00.3.31up to date
 itoa^0.4.31.0.11out of date
 native-tls^0.20.2.12up to date
 percent-encoding^2.12.3.1up to date
 pin-project-lite^0.20.2.15up to date
 r2d2^0.8.80.8.10up to date
 rand^0.80.8.5up to date
 sha1>=0.2, <0.70.10.6out of date
 tokio ⚠️^11.41.1maybe insecure
 tokio-native-tls^0.30.3.1up to date
 tokio-util^0.60.7.12out of date
 url^2.12.5.3up to date

Dev dependencies

(10 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 assert_approx_eq^1.01.1.0up to date
 criterion^0.30.5.1out of date
 fnv^1.0.51.0.7up to date
 futures^0.30.3.31up to date
 partial-io^0.30.5.4out of date
 quickcheck^0.61.0.3out of date
 rand^0.80.8.5up to date
 socket2^0.30.5.7out of date
 tempfile^3.23.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);