Deps.rs

actix-redis 0.9.2

[![dependency status](https://deps.rs/crate/actix-redis/0.9.2/status.svg)](https://deps.rs/crate/actix-redis/0.9.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 actix-redis

Dependencies

(18 total, 13 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 actix^0.10.00.13.3out of date
 actix-http ⚠️^2.0.03.6.0out of date
 actix-rt^1.1.12.9.0out of date
 actix-service^1.0.62.0.2out of date
 actix-session^0.4.00.9.0out of date
 actix-utils^2.0.03.0.1out of date
 actix-web^3.0.04.5.1out of date
 backoff^0.2.10.4.0out of date
 derive_more^0.99.20.99.17up to date
 futures-util^0.3.70.3.30up to date
 log^0.4.60.4.21up to date
 rand^0.7.00.8.5out of date
 redis-async^0.6.30.17.1out of date
 serde^1.0.1011.0.201up to date
 serde_json^1.0.401.0.117up to date
 time^0.2.230.3.36out of date
 tokio ⚠️^0.2.61.37.0out of date
 tokio-util^0.3.00.7.11out of date

Security Vulnerabilities

actix-http: Potential request smuggling capabilities due to lack of input validation

RUSTSEC-2021-0081

Affected versions of this crate did not properly detect invalid requests that could allow HTTP/1 request smuggling (HRS) attacks when running alongside a vulnerable front-end proxy server. This can result in leaked internal and/or user data, including credentials, when the front-end proxy is also vulnerable.

Popular front-end proxies and load balancers already mitigate HRS attacks so it is recommended that they are also kept up to date; check your specific set up. You should upgrade even if the front-end proxy receives exclusively HTTP/2 traffic and connects to the back-end using HTTP/1; several downgrade attacks are known that can also expose HRS 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.