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.
in_stream(15 total, 11 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| crossbeam-channel | ^0.3 | 0.5.15 | out of date |
| env_logger | ^0.6 | 0.11.8 | out of date |
| lazy_static | =1.4.0 | 1.5.0 | out of date |
| log | ^0.4 | 0.4.27 | up to date |
| nanoid | ^0.2 | 0.4.0 | out of date |
| native-tls | ^0.2 | 0.2.14 | up to date |
| net2 | ^0.2 | 0.2.39 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.73 | maybe insecure |
| parking_lot | ^0.9 | 0.12.4 | out of date |
| serde | =1.0.104 | 1.0.219 | out of date |
| serde_derive | =1.0.104 | 1.0.219 | out of date |
| serde_json | =1.0.47 | 1.0.140 | out of date |
| shrinkwraprs | ^0.2 | 0.3.0 | out of date |
| tungstenite ⚠️ | ^0.9.2 | 0.27.0 | out of date |
| 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).
openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.
In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).
The maintainers thank quitbug for reporting this vulnerability to us.