This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate serenity

Dependencies

(20 total, 9 outdated, 1 insecure)

CrateRequiredLatestStatus
 async-trait^0.1.90.1.92up to date
 async-tungstenite^0.9.20.35.0out of date
 base64^0.130.23.1out of date
 bitflags^1.12.13.2out of date
 bytes^0.51.12.1out of date
 chrono^0.4.100.4.45up to date
 command_attr^0.3.80.5.4out of date
 flate2^1.0.131.1.10up to date
 futures^0.30.3.34up to date
 percent-encoding^2.12.3.2up to date
 reqwest^0.100.13.5out of date
 serde^1.0.1031.0.229up to date
 serde_json^11.0.151up to date
 serenity-voice-model^0.1.10.3.0out of date
 static_assertions^1.11.1.0up to date
 tokio ⚠️^0.21.53.1insecure
 tracing^0.1.230.1.44up to date
 typemap_rev^0.1.30.4.0out of date
 url^2.12.5.8up to date
 uwl^0.6.00.6.0up to date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 http^0.21.5.0out of date
 tokio-test^0.40.4.6up to date

Security Vulnerabilities

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.