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 suppaftp

Dependencies

(12 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-native-tls^0.50.5.0up to date
 async-std^1.101.13.0up to date
 async-tls^0.130.13.0up to date
 async-trait^0.1.640.1.83up to date
 chrono ⚠️^0.40.4.38maybe insecure
 futures-lite^2.0.02.5.0up to date
 lazy-regex^33.3.0up to date
 log^0.40.4.22up to date
 native-tls^0.20.2.12up to date
 pin-project^11.1.7up to date
 rustls ⚠️^0.230.23.16maybe insecure
 thiserror^12.0.3out of date

Dev dependencies

(6 total, all up-to-date)

CrateRequiredLatestStatus
 async-attributes^1.1.21.1.2up to date
 env_logger^0.110.11.5up to date
 pretty_assertions^1.0.01.4.1up to date
 rand^0.8.40.8.5up to date
 serial_test^3.03.2.0up to date
 webpki-roots^0.260.26.6up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

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.