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 http2

Dependencies

(13 total, 1 possibly insecure)

CrateRequiredLatestStatus
 atomic-waker^1.0.01.1.2up to date
 bytes^1.11.11.12.0up to date
 fnv^1.0.51.0.7up to date
 futures-core^0.30.3.32up to date
 futures-sink^0.30.3.32up to date
 http^1.4.21.4.2up to date
 indexmap^22.14.0up to date
 parking_lot^0.12.40.12.5up to date
 slab^0.4.20.4.12up to date
 smallvec^1.15.01.15.2up to date
 tokio ⚠️^11.52.3maybe insecure
 tokio-util^0.7.10.7.18up to date
 tracing^0.10.1.44up to date

Dev dependencies

(12 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.100.11.10out of date
 h2 ⚠️^0.40.4.15maybe insecure
 hex^0.4.30.4.3up to date
 quickcheck^1.0.31.1.0up to date
 rand^0.8.40.10.1out of date
 serde^1.0.01.0.228up to date
 serde_json^1.0.01.0.150up to date
 tokio ⚠️^11.52.3maybe insecure
 tokio-rustls^0.260.26.4up to date
 tracing^0.10.1.44up to date
 walkdir^2.3.22.5.0up to date
 webpki-roots^11.0.8up 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.