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 fred

Dependencies

(41 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arc-swap^1.71.7.1up to date
 async-trait^0.10.1.88up to date
 bytes^1.61.10.1up to date
 bytes-utils^0.1.30.1.4up to date
 float-cmp^0.100.10.0up to date
 fred-macros^0.10.1.0up to date
 futures^0.30.3.31up to date
 futures-io^0.30.3.31up to date
 futures-lite^2.32.6.0up to date
 glob-match^0.2.10.2.1up to date
 glommio^0.9.00.9.0up to date
 hickory-resolver^0.24.10.25.1out of date
 local-sync^0.1.10.1.1up to date
 log^0.40.4.27up to date
 monoio^0.2.40.2.4up to date
 monoio-codec^0.3.40.3.4up to date
 monoio-native-tls^0.4.00.4.0up to date
 monoio-rustls^0.4.00.4.0up to date
 native-tls^0.20.2.14up to date
 nom^7.18.0.0out of date
 oneshot^0.1.80.1.11up to date
 parking_lot^0.120.12.3up to date
 pin-project^1.1.51.1.10up to date
 rand^0.80.9.1out of date
 redis-protocol^6.0.06.0.0up to date
 rustls ⚠️^0.230.23.26maybe insecure
 rustls-native-certs^0.80.8.1up to date
 semver^1.01.0.26up to date
 serde_json^11.0.140up to date
 sha-1^0.100.10.1up to date
 socket2^0.50.5.9up to date
 tokio^1.341.44.2up to date
 tokio-native-tls^0.30.3.1up to date
 tokio-rustls^0.260.26.2up to date
 tokio-stream^0.10.1.17up to date
 tokio-util^0.70.7.14up to date
 tracing^0.10.1.41up to date
 tracing-futures^0.20.2.5up to date
 trust-dns-resolver^0.230.23.2up to date
 url^2.42.5.4up to date
 urlencoding^2.12.1.3up to date

Dev dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 actix-web^4.9.04.10.2up to date
 axum^0.70.8.3out of date
 maplit^1.01.0.2up to date
 pretty_env_logger^0.50.5.0up to date
 serde^1.01.0.219up to date
 tokio-stream^0.10.1.17up 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.