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-proto

Dependencies

(14 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.661.0.89up to date
 async-trait^0.1.580.1.82up to date
 chrono^0.4.340.4.38up to date
 futures-core^0.3.280.3.30up to date
 http^0.2.81.1.0out of date
 portpicker^0.1.10.1.1up to date
 prost^0.12.10.13.2out of date
 prost-types^0.12.10.13.2out of date
 serde_json^1.0.891.0.128up to date
 shuttle-common^0.47.00.47.0up to date
 tokio ⚠️^1.22.01.40.0maybe insecure
 tonic^0.10.20.12.2out of date
 tower^0.4.130.5.1out of date
 tracing^0.1.370.1.40up 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);