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 indicatif

Dependencies

(10 total, 1 possibly insecure)

CrateRequiredLatestStatus
 console^0.150.15.8up to date
 futures-core^0.30.3.30up to date
 instant^0.10.1.13up to date
 number_prefix^0.40.4.0up to date
 portable-atomic^1.0.01.7.0up to date
 rayon^1.11.10.0up to date
 tokio ⚠️^11.38.1maybe insecure
 unicode-segmentation^11.11.0up to date
 unicode-width^0.10.1.13up to date
 vt100^0.15.10.15.2up to date

Dev dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 clap^44.5.9up to date
 futures^0.30.3.30up to date
 once_cell^11.19.0up to date
 pretty_assertions^1.4.01.4.0up to date
 rand^0.80.8.5up to date
 tokio ⚠️^11.38.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);