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 redis

Dependencies

(21 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arc-swap^1.1.01.5.1up to date
 async-native-tls^0.30.4.0out of date
 async-std^1.5.01.12.0up to date
 async-trait^0.1.240.1.57up to date
 bytes^11.2.1up to date
 combine^4.64.6.6up to date
 crc16^0.40.4.0up to date
 dtoa^0.41.0.3out of date
 futures^0.3.30.3.23up to date
 futures-util^0.3.150.3.23up to date
 itoa^0.4.31.0.3out of date
 native-tls^0.20.2.10up to date
 percent-encoding^2.12.1.0up to date
 pin-project-lite^0.20.2.9up to date
 r2d2^0.8.80.8.10up to date
 rand^0.80.8.5up to date
 sha1>=0.2, <0.70.10.1out of date
 tokio ⚠️^11.20.1maybe insecure
 tokio-native-tls^0.30.3.0up to date
 tokio-util^0.60.7.3out of date
 url^2.12.2.2up to date

Dev dependencies

(10 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 assert_approx_eq^1.01.1.0up to date
 criterion^0.30.3.6up to date
 fnv^1.0.51.0.7up to date
 futures^0.30.3.23up to date
 partial-io^0.30.5.0out of date
 quickcheck^0.61.0.3out of date
 rand^0.80.8.5up to date
 socket2^0.30.4.4out of date
 tempfile^3.23.3.0up to date
 tokio ⚠️^11.20.1maybe insecure

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.