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 cargo-run

Dependencies

(12 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 clap^4.5.74.6.1up to date
 clap_complete^4.5.614.6.5up to date
 colored^3.03.1.1up to date
 dialoguer^0.110.12.0out of date
 emoji^0.2.10.2.1up to date
 indicatif^0.180.18.4up to date
 notify^6.18.2.0out of date
 notify-debouncer-full^0.30.7.0out of date
 serde^1.0.2031.0.228up to date
 serde_json^1.01.0.149up to date
 tokio ⚠️^11.52.3maybe insecure
 toml^0.91.1.2+spec-1.1.0out of date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 assert_cmd^2.0.142.2.2up to date
 predicates^3.1.03.1.4up to date
 tempfile^3.103.27.0up 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);