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 h3

Dependencies

(7 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.6.0up to date
 fastrand^2.0.12.0.2up to date
 futures-util^0.30.3.30up to date
 http^0.2.91.1.0out of date
 pin-project-lite^0.20.2.14up to date
 tokio ⚠️^11.37.0maybe insecure
 tracing^0.1.400.1.40up to date

Dev dependencies

(11 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 assert_matches^1.5.01.5.0up to date
 futures^0.3.280.3.30up to date
 futures-util^0.30.3.30up to date
 proptest^11.4.0up to date
 quinn^0.100.10.2up to date
 quinn-proto ⚠️^0.100.10.6maybe insecure
 rcgen^0.11.30.13.1out of date
 rustls^0.210.23.4out of date
 tokio ⚠️^11.37.0maybe insecure
 tokio-util^0.7.90.7.10up to date
 tracing-subscriber^0.30.3.18up 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);

quinn-proto: Denial of service in Quinn servers

RUSTSEC-2023-0063

Receiving QUIC frames containing a frame with unknown frame type could lead to a panic. Unfortunately this is issue was not found by our fuzzing infrastructure.

Thanks to the QUIC Tester research group for reporting this issue.