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, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-core^0.30.3.30up to date
 futures-util^0.30.3.30up to date
 hdrhistogram^6.07.5.4out of date
 indexmap^1.0.22.2.6out of date
 pin-project^11.1.5up to date
 rand^0.80.8.5up to date
 slab^0.40.4.9up to date
 tokio ⚠️^11.37.0maybe insecure
 tokio-stream^0.1.00.1.15up to date
 tokio-util^0.6.30.7.10out of date
 tower-layer^0.3.10.3.2up to date
 tower-service^0.30.3.2up to date
 tracing^0.1.20.1.40up to date

Dev dependencies

(9 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.30.3.30up to date
 hdrhistogram^6.07.5.4out of date
 http^0.21.1.0out of date
 quickcheck^0.91.0.3out of date
 tokio ⚠️^11.37.0maybe insecure
 tokio-stream^0.10.1.15up to date
 tokio-test^0.40.4.4up to date
 tower-test^0.40.4.0up to date
 tracing-subscriber^0.2.140.3.18out 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);