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-api-client

Dependencies

(17 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.661.0.93up to date
 async-trait^0.1.580.1.83up to date
 headers^0.3.80.4.0out of date
 http^0.2.81.1.0out of date
 percent-encoding^2.22.3.1up to date
 reqwest^0.11.130.12.9out of date
 reqwest-middleware^0.2.50.4.0out of date
 rmp-serde^1.1.11.3.0up to date
 serde^1.0.1481.0.215up to date
 serde_json^1.0.891.0.132up to date
 shuttle-common^0.48.00.49.0out of date
 task-local-extensions^0.1.40.1.4up to date
 tokio ⚠️^1.22.01.41.1maybe insecure
 tokio-tungstenite^0.20.10.24.0out of date
 tracing^0.1.370.1.40up to date
 url^2.4.02.5.3up to date
 uuid^1.2.21.11.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);