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, 10 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.750.1.89up to date
 bitflags^2.4.12.9.4up to date
 bytes^1.5.01.10.1up to date
 chrono^0.4.310.4.42up to date
 dashmap^5.5.36.1.0out of date
 derive_more^0.99.172.0.1out of date
 futures-util^0.3.290.3.31up to date
 getrandom^0.2.110.3.3out of date
 lazy_static^1.4.01.5.0up to date
 libc^0.20.2.175up to date
 md-5^0.10.60.10.6up to date
 moka^0.11.30.12.10out of date
 prometheus^0.13.30.14.0out of date
 proxy-protocol^0.5.00.5.0up to date
 rustls ⚠️^0.21.100.23.31out of date
 rustls-pemfile^1.0.42.2.0out of date
 slog^2.7.02.7.0up to date
 slog-stdlog^4.1.14.1.1up to date
 thiserror^1.0.512.0.16out of date
 tokio^1.35.11.47.1up to date
 tokio-rustls^0.24.10.26.2out of date
 tokio-util^0.7.100.7.16up to date
 tracing^0.1.400.1.41up to date
 tracing-attributes^0.1.270.1.30up to date
 uuid^1.6.11.18.1up to date
 x509-parser^0.14.00.18.0out of date

Dev dependencies

(2 total, all up-to-date)

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