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 tokio-tower

Dependencies

(9 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tower-service^0.30.3.3up to date
 tower^0.40.5.1out of date
 futures-util^0.30.3.31up to date
 futures-core^0.30.3.31up to date
 futures-sink^0.30.3.31up to date
 tokio ⚠️^1.01.41.1maybe insecure
 crossbeam^0.80.8.4up to date
 tracing^0.1.20.1.40up to date
 pin-project^1.01.1.7up to date

Dev dependencies

(7 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.01.41.1maybe insecure
 serde^1.01.0.215up to date
 serde_derive^1.01.0.215up to date
 async-bincode^0.60.7.2out of date
 slab^0.40.4.9up to date
 tokio-test^0.40.4.4up to date
 tower-test^0.40.4.0up 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);