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 streamcatcher

Dependencies

(8 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-compat^0.20.2.4up to date
 async-std^11.13.0up to date
 async-trait^0.10.1.83up to date
 crossbeam-utils^0.80.8.21up to date
 futures-util^0.30.3.31up to date
 loom^0.50.7.2out of date
 smol^12.0.2out of date
 tokio ⚠️^11.42.0maybe insecure

Dev dependencies

(6 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^11.13.0up to date
 criterion^0.30.5.1out of date
 futures^0.30.3.31up to date
 smol^12.0.2out of date
 synchronoise^11.0.1up to date
 tokio ⚠️^11.42.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);