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

Dependencies

(18 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix-rt^2.0.02.10.0up to date
 actix_derive^0.6.00.6.2up to date
 bitflags^1.22.9.1out of date
 bytes^11.10.1up to date
 crossbeam-channel^0.50.5.15up to date
 futures-core^0.3.70.3.31up to date
 futures-sink^0.3.70.3.31up to date
 futures-task^0.3.70.3.31up to date
 futures-util^0.3.70.3.31up to date
 log^0.40.4.27up to date
 once_cell^1.51.21.3up to date
 parking_lot^0.110.12.4out of date
 pin-project-lite^0.20.2.16up to date
 smallvec^1.6.11.15.1up to date
 tokio ⚠️^11.46.0maybe insecure
 tokio-util^0.60.7.15out of date
 trust-dns-proto^0.20.00.23.2out of date
 trust-dns-resolver^0.20.00.23.2out of 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);