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 tower

Dependencies

(13 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-core^0.3.220.3.31up to date
 futures-util^0.3.220.3.31up to date
 hdrhistogram^7.07.5.4up to date
 indexmap^2.0.22.6.0up to date
 pin-project-lite^0.2.70.2.15up to date
 slab^0.40.4.9up to date
 sync_wrapper^0.1.11.0.1out of date
 tokio ⚠️^1.6.21.41.1maybe insecure
 tokio-stream^0.1.00.1.16up to date
 tokio-util^0.7.00.7.12up to date
 tower-layer^0.3.30.3.3up to date
 tower-service^0.3.30.3.3up to date
 tracing^0.1.20.1.40up to date

Dev dependencies

(13 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.3.220.3.31up to date
 hdrhistogram^7.07.5.4up to date
 http^0.21.1.0out of date
 lazy_static^1.4.01.5.0up to date
 pin-project-lite^0.2.70.2.15up to date
 quickcheck^11.0.3up to date
 rand^0.80.8.5up to date
 tokio ⚠️^1.6.21.41.1maybe insecure
 tokio-stream^0.1.00.1.16up to date
 tokio-test^0.40.4.4up to date
 tower-test^0.40.4.0up to date
 tracing^0.1.20.1.40up to date
 tracing-subscriber^0.30.3.18up 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);