Deps.rs

actix-redis 0.9.1

[![dependency status](https://deps.rs/crate/actix-redis/0.9.1/status.svg)](https://deps.rs/crate/actix-redis/0.9.1)

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

Crate actix-redis

Dependencies

(18 total, 14 outdated, 1 insecure)

CrateRequiredLatestStatus
 actix^0.10.00.13.5out of date
 actix-http^2.0.03.18.12out of date
 actix-rt^1.1.12.15.0out of date
 actix-service^1.0.62.0.3out of date
 actix-session^0.4.00.11.0out of date
 actix-utils^2.0.03.0.2out of date
 actix-web^3.0.04.15.0out of date
 backoff^0.2.10.4.0out of date
 derive_more^0.99.22.1.1out of date
 futures-util^0.3.50.3.34up to date
 log^0.4.60.4.34up to date
 rand^0.7.00.10.3out of date
 redis-async^0.6.30.18.0out of date
 serde^1.0.1011.0.229up to date
 serde_json^1.0.401.0.151up to date
 time^0.2.90.3.55out of date
 tokio ⚠️^0.2.61.53.1insecure
 tokio-util^0.3.00.7.19out of 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.