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.

Crate in_stream

Dependencies

(15 total, 10 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 crossbeam-channel^0.30.5.12out of date
 env_logger^0.60.11.3out of date
 lazy_static=1.4.01.4.0up to date
 log^0.40.4.21up to date
 nanoid^0.20.4.0out of date
 native-tls^0.20.2.11up to date
 net2^0.20.2.39up to date
 openssl ⚠️^0.100.10.64maybe insecure
 parking_lot^0.90.12.2out of date
 serde=1.0.1041.0.200out of date
 serde_derive=1.0.1041.0.200out of date
 serde_json=1.0.471.0.116out of date
 shrinkwraprs^0.20.3.0out of date
 tungstenite ⚠️^0.9.20.21.0out of date
 url2^0.0.40.0.6out of date

Security Vulnerabilities

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.

tungstenite: Tungstenite allows remote attackers to cause a denial of service

RUSTSEC-2023-0065

The 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).