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(8 total, 6 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes | ^0.4.6 | 1.6.0 | out of date |
| futures | ^0.1.17 | 0.3.30 | out of date |
| native-tls | ^0.1.5 | 0.2.11 | out of date |
| tokio-core | ^0.1.9 | 0.1.18 | up to date |
| tokio-dns-unofficial | ^0.1.1 | 0.4.0 | out of date |
| tokio-io | ^0.1.2 | 0.1.13 | up to date |
| tokio-tls | ^0.1.4 | 0.3.1 | out of date |
| tungstenite ⚠️ | ^0.5.3 | 0.21.0 | out of date |
(2 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tokio-core | ^0.1.12 | 0.1.18 | up to date |
| url | ^1.6.0 | 2.5.0 | out of 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).