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 s2n-quic-platform

Dependencies

(12 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bach^0.1.00.1.2up to date
 bolero-generator^0.130.13.5up to date
 cfg-if^11.0.4up to date
 futures^0.30.3.32up to date
 lazy_static^11.5.0up to date
 libc^0.20.2.186up to date
 s2n-quic-core=0.81.00.81.0up to date
 s2n-quic-xdp=0.81.00.81.0up to date
 socket2^0.60.6.4up to date
 tokio ⚠️^11.52.3maybe insecure
 tracing^0.10.1.44up to date
 turmoil^0.7.00.7.2up to date

Dev dependencies

(8 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bach^0.1.00.1.2up to date
 bolero^0.130.13.4up to date
 bolero-generator^0.130.13.5up to date
 futures^0.30.3.32up to date
 insta^11.47.2up to date
 tempfile^33.27.0up to date
 tokio ⚠️^11.52.3maybe insecure
 tracing^0.10.1.44up 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);