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 async-bincode

Dependencies

(8 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bincode^1.3.21.3.3up to date
 byteorder^1.0.01.5.0up to date
 bytes^1.01.8.0up to date
 futures-core^0.3.00.3.31up to date
 futures-io^0.3.210.3.31up to date
 futures-sink^0.3.00.3.31up to date
 serde^1.0.81.0.214up to date
 tokio ⚠️^1.01.41.0maybe insecure

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.11.01.13.0up to date
 futures^0.3.00.3.31up to date
 tokio ⚠️^1.01.41.0maybe 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);