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 scylla

Dependencies

(26 total, 2 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 arc-swap^1.3.01.7.1up to date
 async-trait^0.1.560.1.89up to date
 base64^0.22.10.22.1up to date
 bytes^1.0.11.10.1up to date
 chrono^0.4.320.4.42up to date
 dashmap^6.06.1.0up to date
 futures^0.3.60.3.31up to date
 hashbrown ⚠️^0.150.16.0out of date
 histogram^0.11.10.11.3up to date
 itertools^0.14.00.14.0up to date
 openssl ⚠️^0.10.700.10.73maybe insecure
 rand^0.9.00.9.2up to date
 rand_pcg^0.9.00.9.0up to date
 rustls ⚠️^0.230.23.32maybe insecure
 scylla-cql^1.3.11.3.1up to date
 serde^1.01.0.227up to date
 serde_yaml^0.9.140.9.34+deprecatedup to date
 smallvec^1.8.01.15.1up to date
 socket2^0.5.30.6.0out of date
 thiserror^2.0.62.0.16up to date
 tokio^1.401.47.1up to date
 tokio-openssl^0.6.10.6.5up to date
 tokio-rustls^0.260.26.4up to date
 tracing^0.1.360.1.41up to date
 url^2.3.12.5.7up to date
 uuid^1.01.18.1up to date

Dev dependencies

(12 total, 1 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.981.0.100up to date
 assert_matches^1.5.01.5.0up to date
 bigdecimal^0.40.4.8up to date
 criterion^0.60.7.0out of date
 ntest^0.9.30.9.3up to date
 num-bigint^0.40.4.6up to date
 rand_chacha^0.9.00.9.0up to date
 scylla-proxy^0.0.40.0.4up to date
 tempfile^3.193.23.0up to date
 time^0.30.3.44up to date
 tokio^1.341.47.1up to date
 tracing-subscriber^0.3.140.3.20up 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.

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.

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.