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, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 byteorder^1.3.21.5.0up to date
 bytes^1.01.8.0up to date
 data-encoding^22.6.0up to date
 http^1.01.1.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.17maybe insecure
 rustls-native-certs^0.7.00.8.0out of date
 rustls-pki-types^1.01.10.0up to date
 sha1^0.100.10.6up to date
 thiserror^1.0.232.0.3out of date
 url^2.1.02.5.3up to date
 utf-8^0.7.50.7.6up to date
 webpki-roots^0.260.26.6up to date

Dev dependencies

(5 total, 1 outdated)

CrateRequiredLatestStatus
 criterion^0.5.00.5.1up to date
 env_logger^0.10.00.11.5out of date
 input_buffer^0.5.00.5.0up to date
 rand^0.8.40.8.5up to date
 socket2^0.5.50.5.7up to date

Security Vulnerabilities

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.