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 rustis

Dependencies

(28 total, 2 possibly insecure)

CrateRequiredLatestStatus
 async-native-tls^0.50.5.0up to date
 async-std^1.131.13.2up to date
 atoi^2.02.0.0up to date
 bb8^0.90.9.0up to date
 bytes^1.101.10.1up to date
 crc16^0.40.4.0up to date
 dashmap^6.16.1.0up to date
 dtoa^1.01.0.10up to date
 fast-float2 ⚠️^0.20.2.3maybe insecure
 futures-channel^0.30.3.31up to date
 futures-util^0.30.3.31up to date
 itoa^1.01.0.15up to date
 log^0.40.4.28up to date
 memchr^2.72.7.6up to date
 moka^0.120.12.11up to date
 native-tls^0.20.2.14up to date
 rand^0.90.9.2up to date
 rustls ⚠️^0.230.23.32maybe insecure
 serde^1.01.0.228up to date
 serde_json^1.01.0.145up to date
 smallvec^1.151.15.1up to date
 socket2^0.60.6.0up to date
 tokio^1.461.47.1up to date
 tokio-native-tls^0.30.3.1up to date
 tokio-rustls^0.260.26.4up to date
 tokio-util^0.70.7.16up to date
 url^2.52.5.7up to date
 webpki-roots^1.01.0.2up to date

Dev dependencies

(11 total, 1 outdated)

CrateRequiredLatestStatus
 actix-web^4.114.11.0up to date
 axum^0.80.8.6up to date
 criterion^0.60.7.0out of date
 env_logger^0.110.11.8up to date
 fred^10.110.1.0up to date
 rand^0.90.9.2up to date
 redis^0.320.32.7up to date
 rustls-pemfile^2.22.2.0up to date
 serial_test^3.23.2.0up to date
 smallvec^1.151.15.1up to date
 tokio^1.461.47.1up to date

Security Vulnerabilities

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.

fast-float2: Segmentation fault due to lack of bound check

RUSTSEC-2025-0002

In this case, the "fast_float2::common::AsciiStr::first" method within the "AsciiStr" struct uses the unsafe keyword to reading from memory without performing bounds checking. Specifically, it directly dereferences a pointer offset by "self.ptr". Because of the above reason, the method accesses invalid memory address when it takes an empty string as its input. This approach violates Rust’s memory safety guarantees, as it can lead to invalid memory access if empty buffer is provided.