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-toolbox

Dependencies

(19 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix~0.130.13.5up to date
 actix-session~0.70.10.1out of date
 actix-web~44.10.2up to date
 actix-web-actors~44.3.1+deprecatedup to date
 anyhow~11.0.97up to date
 async-trait~0.10.1.87up to date
 byte-unit~45.1.6out of date
 chrono>=0.4.200.4.40up to date
 futures~0.30.3.31up to date
 log~0.40.4.26up to date
 log4rs~11.3.0up to date
 openidconnect~24.0.0out of date
 pin-project~11.1.10up to date
 rand~0.80.9.0out of date
 rorm~0.50.6.4out of date
 serde~11.0.219up to date
 serde_json~11.0.140up to date
 tokio ⚠️~11.44.1maybe insecure
 uuid~11.15.1up 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);