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 serenity

Dependencies

(31 total, 10 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.90.1.83up to date
 async-tungstenite^0.170.28.2out of date
 base64^0.210.22.1out of date
 bitflags^1.32.6.0out of date
 bytes^1.01.9.0up to date
 cfg-if^1.0.01.0.0up to date
 chrono ⚠️^0.4.100.4.39maybe insecure
 command_attr^0.4.20.5.3out of date
 dashmap^5.1.06.1.0out of date
 time^0.3.60.3.37up to date
 flate2^1.0.131.0.35up to date
 futures^0.30.3.31up to date
 levenshtein^1.0.51.0.5up to date
 mime^0.3.160.3.17up to date
 mime_guess^2.02.0.5up to date
 moka^0.90.12.8out of date
 parking_lot^0.120.12.3up to date
 percent-encoding^2.12.3.1up to date
 reqwest^0.11.70.12.9out of date
 rustversion^1.0.71.0.18up to date
 serde^1.0.1301.0.216up to date
 serde-value^0.70.7.0up to date
 serde_json^1.0.751.0.134up to date
 serenity-voice-model^0.1.10.2.0out of date
 simd-json^0.4.140.14.3out of date
 static_assertions^1.11.1.0up to date
 tokio ⚠️^11.42.0maybe insecure
 tracing^0.1.230.1.41up to date
 typemap_rev^0.1.30.3.0out of date
 url^2.12.5.4up to date
 uwl^0.6.00.6.0up to date

Dev dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 http^0.21.2.0out of date
 serde_test^11.0.177up to date
 tokio-test^0.40.4.4up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

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