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 rocket

Dependencies

(31 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-stream^0.3.20.3.6up to date
 async-trait^0.1.430.1.83up to date
 atomic^0.50.6.0out of date
 binascii^0.10.1.4up to date
 bytes^1.01.8.0up to date
 either^11.13.0up to date
 figment^0.10.60.10.19up to date
 futures^0.3.00.3.31up to date
 indexmap^22.6.0up to date
 log^0.40.4.22up to date
 memchr^22.7.4up to date
 multer^3.0.03.1.0up to date
 num_cpus^1.01.16.0up to date
 parking_lot^0.120.12.3up to date
 pin-project-lite^0.20.2.15up to date
 rand^0.80.8.5up to date
 ref-cast^1.01.0.23up to date
 rmp-serde^11.3.0up to date
 rocket_codegen^0.5.10.5.1up to date
 rocket_http^0.5.10.5.1up to date
 serde^1.01.0.214up to date
 serde_json^1.0.261.0.132up to date
 state^0.60.6.0up to date
 tempfile^33.14.0up to date
 time^0.30.3.36up to date
 tokio ⚠️^1.6.11.41.1maybe insecure
 tokio-stream^0.1.60.1.16up to date
 tokio-util^0.70.7.12up to date
 ubyte^0.10.20.10.4up to date
 uuid^11.11.0up to date
 yansi^1.0.11.0.1up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 figment^0.100.10.19up to date
 pretty_assertions^11.4.1up 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);