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 bitbucket_server_cli

Dependencies

(11 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 atomic-counter^1.01.0.1up to date
 clap^2.334.5.4out of date
 dialoguer^0.80.11.0out of date
 futures^0.30.3.30up to date
 generic_error^0.20.2.0up to date
 indicatif^0.160.17.8out of date
 pickledb^0.40.5.1out of date
 reqwest^0.110.12.3out of date
 serde^1.01.0.198up to date
 structopt^0.30.3.26up to date
 tokio ⚠️^1.111.37.0maybe insecure

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 rand^0.80.8.5up to date
 tokio-test^0.40.4.4up to date

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