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-util

Dependencies

(12 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.6.0up to date
 futures-channel^0.30.3.30up to date
 futures-util^0.3.160.3.30up to date
 http^1.01.1.0up to date
 http-body^1.0.01.0.0up to date
 hyper^1.3.01.3.1up to date
 pin-project-lite^0.2.40.2.14up to date
 socket2^0.50.5.7up to date
 tokio ⚠️^11.38.0maybe insecure
 tower^0.4.10.4.13up to date
 tower-service^0.30.3.2up to date
 tracing^0.10.1.40up to date

Dev dependencies

(7 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.6.0up to date
 http-body-util^0.1.00.1.2up to date
 hyper^1.3.01.3.1up to date
 pnet_datalink^0.34.00.35.0out of date
 pretty_env_logger^0.50.5.0up to date
 tokio ⚠️^11.38.0maybe insecure
 tokio-test^0.40.4.4up 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);