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 libunftp

Dependencies

(26 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.750.1.80up to date
 bitflags^2.4.12.5.0up to date
 bytes^1.5.01.6.0up to date
 chrono^0.4.310.4.38up to date
 dashmap^5.5.35.5.3up to date
 derive_more^0.99.170.99.17up to date
 futures-util^0.3.290.3.30up to date
 getrandom^0.2.110.2.15up to date
 lazy_static^1.4.01.4.0up to date
 libc^0.20.2.154up to date
 md-5^0.10.60.10.6up to date
 moka^0.11.30.12.7out of date
 prometheus^0.13.30.13.4up to date
 proxy-protocol^0.5.00.5.0up to date
 rustls ⚠️^0.21.100.23.5out of date
 rustls-pemfile^1.0.42.1.2out of date
 slog^2.7.02.7.0up to date
 slog-stdlog^4.1.14.1.1up to date
 thiserror^1.0.511.0.60up to date
 tokio^1.35.11.37.0up to date
 tokio-rustls^0.24.10.26.0out of date
 tokio-util^0.7.100.7.11up to date
 tracing^0.1.400.1.40up to date
 tracing-attributes^0.1.270.1.27up to date
 uuid^1.6.11.8.0up to date
 x509-parser^0.14.00.16.0out of date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 pretty_assertions^1.4.01.4.0up to date
 tokio^1.35.11.37.0up to 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.