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

(16 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.6.0up to date
 http^11.1.0up to date
 http-body^11.0.0up to date
 tokio ⚠️^11.37.0maybe insecure
 futures-channel^0.30.3.30up to date
 futures-util^0.30.3.30up to date
 h2^0.4.20.4.3up to date
 http-body-util^0.10.1.1up to date
 httparse^1.81.8.0up to date
 httpdate^1.01.0.3up to date
 itoa^11.0.11up to date
 libc^0.20.2.153up to date
 pin-project-lite^0.2.40.2.13up to date
 smallvec^1.121.13.2up to date
 tracing^0.10.1.40up to date
 want^0.30.3.1up to date

Dev dependencies

(11 total, 1 possibly insecure)

CrateRequiredLatestStatus
 form_urlencoded^11.2.1up to date
 futures-channel^0.30.3.30up to date
 futures-util^0.30.3.30up to date
 http-body-util^0.10.1.1up to date
 pretty_env_logger^0.50.5.0up to date
 spmc^0.30.3.0up to date
 serde^1.01.0.197up to date
 serde_json^1.01.0.115up to date
 tokio ⚠️^11.37.0maybe insecure
 tokio-test^0.40.4.4up to date
 tokio-util^0.7.100.7.10up 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);