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 rusty-penguin

Dependencies

(26 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arc-swap^11.7.1up to date
 base64^0.220.22.0up to date
 bytes^11.6.0up to date
 clap^44.5.4up to date
 console-subscriber^0.20.2.0up to date
 futures-util^0.30.3.30up to date
 http^11.1.0up to date
 http-body-util^0.10.1.1up to date
 hyper^11.3.1up to date
 hyper-util^0.10.1.3up to date
 once_cell^11.19.0up to date
 parking_lot^0.120.12.2up to date
 rand^0.80.8.5up to date
 reqwest^0.120.12.4up to date
 rustls ⚠️^0.220.23.5out of date
 rustls-native-certs^0.70.7.0up to date
 rustls-pemfile^22.1.2up to date
 sha1^0.100.10.6up to date
 thiserror^11.0.59up to date
 tokio^1, >=1.23.11.37.0up to date
 tokio-native-tls^0.30.3.1up to date
 tokio-rustls^0.250.26.0out of date
 tokio-tungstenite^0.210.21.0up to date
 tracing^0.10.1.40up to date
 tracing-subscriber^0.30.3.18up to date
 webpki-roots^0.260.26.1up to date

Dev dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 ctor^0.20.2.8up to date
 tempfile^33.10.1up to date
 rcgen^0.120.13.1out of date

Security Vulnerabilities

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.