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.
tokio-tungstenite-wasm(12 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-channel | ^0.3 | 0.3.31 | up to date |
| futures-util | ^0.3 | 0.3.31 | up to date |
| http | ^1.1 | 1.2.0 | up to date |
| httparse | ^1.3 | 1.10.0 | up to date |
| js-sys | ^0.3 | 0.3.77 | up to date |
| native-tls | ^0.2 | 0.2.13 | up to date |
| rustls ⚠️ | ^0.22 | 0.23.21 | out of date |
| thiserror | ^1.0 | 2.0.11 | out of date |
| tokio | ^1.36 | 1.43.0 | up to date |
| tokio-tungstenite | ^0.21 | 0.26.1 | out of date |
| wasm-bindgen | ^0.2 | 0.2.100 | up to date |
| web-sys | ^0.3 | 0.3.77 | up to date |
(3 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| assert-impl | ^0.1 | 0.1.3 | up to date |
| rand | ^0.8 | 0.9.0 | out of date |
| tokio | ^1.36 | 1.43.0 | up to date |
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf 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.