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 twilight-gateway

Dependencies

(14 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bitflags^22.6.0up to date
 fastrand^22.2.0up to date
 flate2^1.0.241.0.35up to date
 futures-core^0.30.3.31up to date
 futures-sink^0.30.3.31up to date
 serde^11.0.215up to date
 serde_json^11.0.133up to date
 simd-json>=0.4, <0.140.14.3out of date
 tokio ⚠️^1.191.41.1maybe insecure
 tokio-websockets^0.50.10.1out of date
 tracing^0.10.1.40up to date
 twilight-gateway-queue^0.16.0-rc.10.15.4up to date
 twilight-http^0.16.0-rc.10.15.4up to date
 twilight-model^0.16.0-rc.10.15.4up to date

Dev dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.93up to date
 serde_test^1.0.1361.0.177up to date
 static_assertions^11.1.0up to date
 tokio ⚠️^1.121.41.1maybe insecure
 tokio-stream^0.10.1.16up to date
 tracing-subscriber^0.30.3.18up 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);