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 discord-sdk

Dependencies

(17 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.82up to date
 app_dirs2^2.32.5.5up to date
 async-trait^0.10.1.80up to date
 bitflags^2.02.5.0up to date
 crossbeam-channel^0.50.5.12up to date
 data-encoding^2.42.5.0up to date
 num-traits^0.20.2.18up to date
 parking_lot^0.120.12.1up to date
 serde^1.01.0.197up to date
 serde_json^1.01.0.115up to date
 serde_repr^0.10.1.19up to date
 thiserror^1.01.0.58up to date
 time^0.30.3.36up to date
 tokio ⚠️^1.8.21.37.0maybe insecure
 tracing^0.10.1.40up to date
 url^2.22.5.0up to date
 winreg^0.510.52.0out of date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 insta^1.211.38.0up 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);