Deps.rs

mysql_async 0.22.2

[![dependency status](https://deps.rs/crate/mysql_async/0.22.2/status.svg)](https://deps.rs/crate/mysql_async/0.22.2)

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 mysql_async

Dependencies

(18 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^0.5.21.6.0out of date
 crossbeam^0.70.8.4out of date
 futures-core^0.30.3.30up to date
 futures-sink^0.30.3.30up to date
 futures-util^0.30.3.30up to date
 mio-named-pipes^0.1.60.1.7up to date
 mysql_common^0.20.00.32.2out of date
 native-tls^0.20.2.11up to date
 percent-encoding^2.1.02.3.1up to date
 pin-project^0.4.61.1.5out of date
 serde^11.0.198up to date
 serde_json^11.0.116up to date
 thiserror^1.0.41.0.59up to date
 tokio ⚠️^0.2.101.37.0out of date
 tokio-tls^0.30.3.1up to date
 tokio-util^0.20.7.10out of date
 twox-hash^11.6.3up to date
 url^2.12.5.0up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 lazy_static^11.4.0up to date
 tempfile^3.1.03.10.1up 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.