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 shuttle-runtime

Dependencies

(15 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.661.0.89up to date
 async-trait^0.1.580.1.82up to date
 colored^2.0.02.1.0up to date
 serde^1.0.1481.0.210up to date
 serde_json^1.0.891.0.128up to date
 shuttle-codegen^0.47.00.47.0up to date
 shuttle-common^0.47.00.47.0up to date
 shuttle-proto^0.47.00.47.0up to date
 shuttle-service^0.47.00.47.0up to date
 strfmt^0.2.20.2.4up to date
 tokio ⚠️^1.22.01.40.0maybe insecure
 tokio-stream^0.1.110.1.16up to date
 tokio-util^0.7.100.7.12up to date
 tonic^0.10.20.12.2out of date
 tracing-subscriber^0.3.160.3.18up to date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 portpicker^0.1.10.1.1up to date
 shuttle-proto^0.47.00.47.0up to date
 shuttle-service^0.47.00.47.0up to date
 uuid^1.2.21.10.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);