Deps.rs

redis 0.27.6

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

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

(40 total, 1 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.8.110.8.11up to date
 arc-swap^1.7.11.7.1up to date
 async-native-tls^0.50.5.0up to date
 async-std^1.13.01.13.0up to date
 async-trait^0.1.830.1.83up to date
 backon^1.2.01.3.0up to date
 bigdecimal^0.4.60.4.7up to date
 bytes^11.9.0up to date
 combine^4.64.6.7up to date
 crc16^0.40.4.0up to date
 futures^0.3.300.3.31up to date
 futures-rustls^0.260.26.0up to date
 futures-util^0.3.150.3.31up to date
 hashbrown ⚠️^0.150.15.2maybe insecure
 itertools^0.13.00.13.0up to date
 itoa^1.01.0.14up to date
 log^0.40.4.22up to date
 native-tls^0.20.2.12up to date
 num-bigint^0.4.60.4.6up to date
 percent-encoding^2.12.3.1up to date
 pin-project-lite^0.20.2.15up to date
 r2d2^0.8.100.8.10up to date
 rand^0.80.8.5up to date
 rust_decimal^1.36.01.36.0up to date
 rustls ⚠️^0.230.23.20maybe insecure
 rustls-native-certs^0.70.8.1out of date
 rustls-pemfile^22.2.0up to date
 rustls-pki-types^11.10.1up to date
 ryu^1.01.0.18up to date
 serde^1.0.2151.0.216up to date
 serde_json^1.0.1331.0.133up to date
 sha1_smol^1.01.0.1up to date
 socket2^0.50.5.8up to date
 tokio ⚠️^11.42.0maybe insecure
 tokio-native-tls^0.30.3.1up to date
 tokio-rustls^0.260.26.1up to date
 tokio-util^0.70.7.13up to date
 url^2.52.5.4up to date
 uuid^1.11.01.11.0up to date
 webpki-roots^0.260.26.7up to date

Dev dependencies

(14 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.94up to date
 assert_approx_eq^1.01.1.0up to date
 criterion^0.40.5.1out of date
 fnv^1.0.51.0.7up to date
 futures^0.30.3.31up to date
 futures-time^33.0.0up to date
 once_cell^11.20.2up to date
 partial-io^0.50.5.4up to date
 quickcheck^1.0.31.0.3up to date
 rand^0.80.8.5up to date
 rstest^0.230.23.0up to date
 socket2^0.50.5.8up to date
 tempfile=3.14.03.14.0up to date
 tokio ⚠️^11.42.0maybe insecure

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);

rustls: rustls network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.

hashbrown: Borsh serialization of HashMap is non-canonical

RUSTSEC-2024-0402

The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding.

This can result in consensus splits and cause equivalent objects to be considered distinct.

This was patched in 0.15.1.