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

CrateRequiredLatestStatus
 bytes^11.4.0up to date
 futures-channel^0.30.3.28up to date
 futures-core^0.30.3.28up to date
 futures-util^0.30.3.28up to date
 h2 ⚠️^0.3.90.3.19maybe insecure
 http^0.20.2.9up to date
 http-body=1.0.0-rc.20.4.5up to date
 http-body-util=0.1.0-rc.2N/Aup to date
 httparse^1.81.8.0up to date
 httpdate^1.01.0.2up to date
 itoa^11.0.6up to date
 libc^0.20.2.146up to date
 pin-project-lite^0.2.40.2.9up to date
 socket2^0.40.5.3out of date
 tokio ⚠️^11.28.2maybe insecure
 tracing^0.10.1.37up to date
 want^0.30.3.0up to date

Dev dependencies

(12 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-util^0.30.3.28up to date
 http-body-util=0.1.0-rc.2N/Aup to date
 matches^0.10.1.10up to date
 num_cpus^1.01.15.0up to date
 pretty_env_logger^0.40.5.0out of date
 serde^1.01.0.163up to date
 serde_json^1.01.0.96up to date
 spmc^0.30.3.0up to date
 tokio ⚠️^11.28.2maybe insecure
 tokio-test^0.40.4.2up to date
 tokio-util^0.70.7.8up to date
 url^2.22.4.0up 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);

h2: Resource exhaustion vulnerability in h2 may lead to Denial of Service (DoS)

RUSTSEC-2023-0034

If an attacker is able to flood the network with pairs of HEADERS/RST_STREAM frames, such that the h2 application is not able to accept them faster than the bytes are received, the pending accept queue can grow in memory usage. Being able to do this consistently can result in excessive memory use, and eventually trigger Out Of Memory.

This flaw is corrected in hyperium/h2#668, which restricts remote reset stream count by default.