This project contains known security vulnerabilities. Find detailed information at the bottom.
tokio-tungstenite(7 total, 1 outdated, 1 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.0 | 0.2.18 | up to date |
| pin-project | ^1.0 | 1.1.13 | up to date |
| tokio | ^1.0.0 | 1.53.1 | up to date |
| tokio-native-tls | ^0.3.0 | 0.3.1 | up to date |
| tungstenite ⚠️ | ^0.12.0 | 0.30.0 | insecure |
(4 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| env_logger | ^0.7 | 0.11.11 | out of date |
| futures-channel | ^0.3 | 0.3.34 | up to 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).