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 tungstenite

Dependencies

(16 total, 1 possibly insecure)

CrateRequiredLatestStatus
 byteorder^1.3.21.5.0up to date
 bytes^1.9.01.9.0up to date
 data-encoding^22.6.0up to date
 http^1.01.2.0up to date
 httparse^1.3.41.9.5up to date
 log^0.4.80.4.22up to date
 native-tls^0.2.30.2.12up to date
 rand^0.8.00.8.5up to date
 rustls ⚠️^0.23.00.23.20maybe insecure
 rustls-native-certs^0.8.00.8.1up to date
 rustls-pki-types^1.01.10.1up to date
 sha1^0.100.10.6up to date
 thiserror^2.0.72.0.9up to date
 url^2.1.02.5.4up to date
 utf-8^0.7.50.7.6up to date
 webpki-roots^0.260.26.7up to date

Dev dependencies

(5 total, all up-to-date)

CrateRequiredLatestStatus
 criterion^0.5.00.5.1up to date
 env_logger^0.110.11.6up to date
 input_buffer^0.5.00.5.0up to date
 rand^0.8.40.8.5up to date
 socket2^0.5.50.5.8up 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.