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

CrateRequiredLatestStatus
 bytes^11.5.0up to date
 futures-channel^0.30.3.30up to date
 futures-core^0.30.3.30up to date
 futures-util^0.30.3.30up to date
 h2 ⚠️^0.3.170.4.2out of date
 http^0.21.0.0out of date
 http-body^0.41.0.0out of date
 httparse^1.81.8.0up to date
 httpdate^1.01.0.3up to date
 itoa^11.0.10up to date
 libc^0.20.2.153up to date
 pin-project-lite^0.2.40.2.13up to date
 socket2>=0.4.7, <0.6.00.5.6up to date
 tokio ⚠️^11.36.0maybe insecure
 tower-service^0.30.3.2up to date
 tracing^0.10.1.40up to date
 want^0.30.3.1up to date

Dev dependencies

(13 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-util^0.30.3.30up to date
 matches^0.10.1.10up to date
 num_cpus^1.01.16.0up to date
 pnet_datalink^0.27.20.34.0out of date
 pretty_env_logger^0.40.5.0out of date
 serde^1.01.0.197up to date
 serde_json^1.01.0.114up to date
 spmc^0.30.3.0up to date
 tokio ⚠️^11.36.0maybe insecure
 tokio-test^0.40.4.3up to date
 tokio-util^0.70.7.10up to date
 tower^0.40.4.13up to date
 url^2.22.5.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-2024-0003

An attacker with an HTTP/2 connection to an affected endpoint can send a steady stream of invalid frames to force the generation of reset frames on the victim endpoint. By closing their recv window, the attacker could then force these resets to be queued in an unbounded fashion, resulting in Out Of Memory (OOM) and high CPU usage.

This fix is corrected in hyperium/h2#737, which limits the total number of internal error resets emitted by default before the connection is closed.