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

Dependencies

(12 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.661.0.93up to date
 async-trait^0.1.580.1.83up to date
 cargo_metadata^0.18.10.19.0out of date
 dunce^1.0.41.0.5up to date
 serde^1.0.1481.0.215up to date
 shuttle-common^0.49.00.49.0up to date
 shuttle-proto^0.49.00.49.0up to date
 strfmt^0.2.20.2.4up to date
 thiserror^22.0.3up to date
 tokio ⚠️^1.22.01.41.1maybe insecure
 toml^0.8.20.8.19up to date
 tracing^0.1.370.1.40up to date

Dev dependencies

(1 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.22.01.41.1maybe insecure

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