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.6.1up 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.240.4.5out of date
 http^0.21.1.0out of date
 http-body^0.41.0.1out of date
 httparse^1.81.9.4up to date
 httpdate^1.01.0.3up to date
 itoa^11.0.11up to date
 libc^0.20.2.155up to date
 pin-project-lite^0.2.40.2.14up to date
 socket2>=0.4.7, <0.6.00.5.7up to date
 tokio ⚠️^11.39.1maybe 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.35.0out of date
 pretty_env_logger^0.40.5.0out of date
 serde^1.01.0.204up to date
 serde_json^1.01.0.120up to date
 spmc^0.30.3.0up to date
 tokio ⚠️^11.39.1maybe insecure
 tokio-test^0.40.4.4up to date
 tokio-util^0.70.7.11up to date
 tower^0.40.4.13up to date
 url^2.22.5.2up 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: Degradation of service in h2 servers with CONTINUATION Flood

RUSTSEC-2024-0332

An attacker can send a flood of CONTINUATION frames, causing h2 to process them indefinitely. This results in an increase in CPU usage.

Tokio task budget helps prevent this from a complete denial-of-service, as the server can still respond to legitimate requests, albeit with increased latency.

More details at "https://seanmonstar.com/blog/hyper-http2-continuation-flood/.

Patches available for 0.4.x and 0.3.x versions.