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

Dependencies

(19 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.6.0up to date
 cfg-if^11.0.0up to date
 cuckoofilter^0.50.5.0up to date
 futures^0.30.3.30up to date
 hash_hasher^22.0.3up to date
 humansize^22.1.3up to date
 rand^0.80.8.5up to date
 rand_chacha^0.30.3.1up to date
 s2n-codec=0.37.00.37.0up to date
 s2n-quic-core=0.37.00.37.0up to date
 s2n-quic-crypto=0.37.00.37.0up to date
 s2n-quic-platform=0.37.00.37.0up to date
 s2n-quic-rustls=0.37.00.37.0up to date
 s2n-quic-tls=0.37.00.37.0up to date
 s2n-quic-tls-default=0.37.00.37.0up to date
 s2n-quic-transport=0.37.00.37.0up to date
 tokio ⚠️^11.37.0maybe insecure
 zerocopy^0.70.7.33up to date
 zeroize^11.7.0up to date

Dev dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bolero^0.100.10.1up to date
 s2n-quic-transport=0.37.00.37.0up to date
 tokio ⚠️^11.37.0maybe insecure
 tracing^0.10.1.40up 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);