This project contains known security vulnerabilities. Find detailed information at the bottom.
tokio-tungstenite(11 total, 5 outdated, 2 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-util | ^0.3 | 0.3.34 | up to date |
| log | ^0.4 | 0.4.34 | up to date |
| native-tls | ^0.2.7 | 0.2.18 | up to date |
| rustls ⚠️ | ^0.20.0 | 0.23.45 | insecure |
| rustls-native-certs | ^0.6.1 | 0.8.4 | out of date |
| tokio | ^1.0.0 | 1.53.1 | up to date |
| tokio-native-tls | ^0.3.0 | 0.3.1 | up to date |
| tokio-rustls | ^0.23.0 | 0.26.6 | out of date |
| tungstenite ⚠️ | ^0.18.0 | 0.30.0 | insecure |
| webpki | ^0.22.0 | 0.22.4 | up to date |
| webpki-roots | ^0.22.1 | 1.0.9 | out of date |
(5 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| env_logger | ^0.9 | 0.11.11 | out of date |
| futures-channel | ^0.3 | 0.3.34 | up to date |
| hyper | ^0.14 | 1.11.1 | out of date |
| tokio | ^1.0.0 | 1.53.1 | up to date |
| url | ^2.0.0 | 2.5.8 | up to date |
tungstenite: Tungstenite allows remote attackers to cause a denial of serviceThe Tungstenite crate through 0.20.0 for Rust allows remote attackers to cause a denial of service (minutes of CPU consumption) via an excessive length of an HTTP header in a client handshake. The length affects both how many times a parse is attempted (e.g., thousands of times) and the average amount of data for each parse attempt (e.g., millions of bytes).
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.