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 par-stream

Dependencies

(12 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.10.01.13.2up to date
 by_address^1.0.41.2.1up to date
 crossbeam^0.8.10.8.4up to date
 dashmap^5.1.06.1.0out of date
 derivative^2.2.02.2.0up to date
 flume^0.10.100.12.0out of date
 futures^0.3.210.3.32up to date
 num_cpus^1.13.11.17.0up to date
 once_cell^1.9.01.21.4up to date
 parking_lot^0.12.00.12.5up to date
 pin-project^1.0.101.1.13up to date
 tokio ⚠️^1.16.11.52.3maybe insecure

Dev dependencies

(6 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.10.01.13.2up to date
 concurrent-slice^0.1.00.1.0up to date
 itertools^0.10.30.14.0out of date
 rand^0.8.40.10.1out of date
 structopt^0.3.260.3.26up to date
 tokio ⚠️^1.16.11.52.3maybe 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);