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 solana-quic-client

Dependencies

(18 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-lock^3.4.03.4.0up to date
 async-trait^0.1.830.1.83up to date
 futures^0.3.310.3.31up to date
 itertools^0.12.10.13.0out of date
 lazy_static^1.5.01.5.0up to date
 log^0.4.220.4.22up to date
 quinn^0.11.60.11.6up to date
 quinn-proto^0.11.90.11.9up to date
 rustls ⚠️^0.23.150.23.20maybe insecure
 solana-connection-cache=2.1.62.1.6up to date
 solana-measure=2.1.62.1.6up to date
 solana-metrics=2.1.62.1.6up to date
 solana-net-utils=2.1.62.1.6up to date
 solana-rpc-client-api=2.1.62.1.6up to date
 solana-sdk=2.1.62.1.6up to date
 solana-streamer=2.1.62.1.6up to date
 thiserror^1.0.652.0.7out of date
 tokio^1.29.11.42.0up to date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 crossbeam-channel^0.5.130.5.14up to date
 solana-logger=2.1.62.1.6up to date
 solana-perf=2.1.62.1.6up 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.