This project contains known security vulnerabilities. Find detailed information at the bottom.
in_stream(15 total, 11 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| crossbeam-channel | ^0.3 | 0.5.17 | out of date |
| env_logger | ^0.6 | 0.11.11 | out of date |
| lazy_static | =1.4.0 | 1.5.0 | out of date |
| log | ^0.4 | 0.4.34 | up to date |
| nanoid | ^0.2 | 0.5.0 | out of date |
| native-tls | ^0.2 | 0.2.18 | up to date |
| net2 | ^0.2 | 0.2.39 | up to date |
| openssl | ^0.10 | 0.10.81 | up to date |
| parking_lot | ^0.9 | 0.12.5 | out of date |
| serde | =1.0.104 | 1.0.229 | out of date |
| serde_derive | =1.0.104 | 1.0.229 | out of date |
| serde_json | =1.0.47 | 1.0.151 | out of date |
| shrinkwraprs | ^0.2 | 0.3.0 | out of date |
| tungstenite ⚠️ | ^0.9.2 | 0.30.0 | insecure |
| url2 | ^0.0.4 | 0.0.6 | 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).