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

CrateRequiredLatestStatus
 base64^0.13.00.22.1out of date
 byteorder^1.3.21.5.0up to date
 bytes^1.01.8.0up to date
 http^0.21.1.0out of 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.20.00.23.16out of date
 rustls-native-certs^0.6.00.8.0out of 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 ⚠️^0.220.22.4maybe insecure
 webpki-roots^0.220.26.6out of date

Dev dependencies

(5 total, 2 outdated)

CrateRequiredLatestStatus
 criterion^0.4.00.5.1out of date
 env_logger^0.10.00.11.5out of date
 input_buffer^0.5.00.5.0up to date
 net2^0.2.370.2.39up to date
 rand^0.8.40.8.5up to date

Security Vulnerabilities

webpki: webpki: CPU denial of service in certificate path building

RUSTSEC-2023-0052

When this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.

Both TLS clients and TLS servers that accept client certificate are affected.

This was previously reported in https://github.com/briansmith/webpki/issues/69 and re-reported recently by Luke Malinowski.

webpki 0.22.1 included a partial fix and webpki 0.22.2 added further fixes.

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.