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 hyper

Dependencies

(17 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.3.0up to date
 futures-channel^0.30.3.25up to date
 futures-core^0.30.3.25up to date
 futures-util^0.30.3.25up to date
 h2^0.3.90.3.15up to date
 http^0.20.2.8up to date
 http-body^0.40.4.5up to date
 httparse^1.81.8.0up to date
 httpdate^1.01.0.2up to date
 itoa^11.0.5up to date
 libc^0.20.2.139up to date
 pin-project-lite^0.2.40.2.9up to date
 socket2^0.4.70.4.7up to date
 tokio ⚠️^11.24.2maybe insecure
 tower-service^0.30.3.2up to date
 tracing^0.10.1.37up to date
 want^0.30.3.0up to date

Dev dependencies

(13 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-util^0.30.3.25up to date
 matches^0.10.1.10up to date
 num_cpus^1.01.15.0up to date
 pnet_datalink^0.27.20.31.0out of date
 pretty_env_logger^0.40.4.0up to date
 serde^1.01.0.152up to date
 serde_json^1.01.0.91up to date
 spmc^0.30.3.0up to date
 tokio ⚠️^11.24.2maybe insecure
 tokio-test^0.40.4.2up to date
 tokio-util^0.70.7.4up to date
 tower^0.40.4.13up to date
 url^2.22.3.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 overriden 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);