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

Dependencies

(13 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix^0.130.13.5up to date
 actix-rt^2.12.10.0up to date
 actix-service^22.0.3up to date
 actix-tls^33.4.0up to date
 actix-web^44.10.2up to date
 backoff^0.4.00.4.0up to date
 derive_more^0.99.72.0.1out of date
 futures-core^0.3.70.3.31up to date
 log^0.4.60.4.26up to date
 redis-async^0.160.17.2out of date
 time^0.30.3.39up to date
 tokio ⚠️^1.18.41.44.1maybe insecure
 tokio-util^0.70.7.14up to date

Dev dependencies

(4 total, 1 outdated)

CrateRequiredLatestStatus
 actix-test^0.1.0-beta.120.1.5up to date
 actix-web^44.10.2up to date
 env_logger^0.100.11.7out of date
 serde^1.0.1011.0.219up 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);