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 h2

Dependencies

(11 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.6.0up to date
 fnv^1.0.51.0.7up to date
 futures-core^0.30.3.30up to date
 futures-sink^0.30.3.30up to date
 futures-util^0.30.3.30up to date
 http^0.21.1.0out of date
 indexmap^1.5.22.2.6out of date
 slab^0.4.20.4.9up to date
 tokio ⚠️^11.37.0maybe insecure
 tokio-util^0.7.10.7.11up to date
 tracing^0.1.210.1.40up to date

Dev dependencies

(10 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.90.11.3out of date
 hex^0.4.30.4.3up to date
 quickcheck^1.0.31.0.3up to date
 rand^0.8.40.8.5up to date
 serde^1.0.01.0.202up to date
 serde_json^1.0.01.0.117up to date
 tokio ⚠️^11.37.0maybe insecure
 tokio-rustls^0.23.20.26.0out of date
 walkdir^2.3.22.5.0up to date
 webpki-roots^0.22.20.26.1out of 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);