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 bitreq

Dependencies

(12 total, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.220.22.1up to date
 log^0.4.00.4.33up to date
 native-tls^0.20.2.18up to date
 rustls^0.23.380.23.41up to date
 rustls-native-certs^0.8.30.8.4up to date
 rustls-webpki^0.103.130.103.13up to date
 serde^1.0.1011.0.228up to date
 serde_json^1.0.01.0.150up to date
 tokio ⚠️^1.01.52.3maybe insecure
 tokio-native-tls^0.30.3.1up to date
 tokio-rustls^0.26.40.26.4up to date
 webpki-roots^1.0.71.0.8up to date

Dev dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 proptest^11.11.0up to date
 tiny_http^0.120.12.0up to date
 tokio ⚠️^1.01.52.3maybe insecure
 url^2.42.5.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);