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 bach

Dependencies

(16 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arr_macro^0.20.2.1up to date
 atomic-waker^11.1.2up to date
 bolero-generator^0.130.13.5up to date
 bytes^11.10.1up to date
 event-listener-strategy^0.5.20.5.4up to date
 futures-core^0.30.3.31up to date
 intrusive-collections^0.90.9.7up to date
 metrics^0.240.24.2up to date
 pin-project-lite^0.20.2.16up to date
 rand^0.90.9.1up to date
 rand_xoshiro^0.70.7.0up to date
 s2n-quic-core^0.570.61.0out of date
 siphasher^11.0.1up to date
 slotmap^11.0.7up to date
 tokio ⚠️^11.46.1maybe insecure
 tracing^0.10.1.41up to date

Dev dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bolero^0.130.13.4up to date
 bytes^11.10.1up to date
 pcap-parser^0.160.16.0up to date
 tokio ⚠️^11.46.1maybe insecure

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);