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, 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.87up to date
 chrono ⚠️^0.40.4.40maybe insecure
 futures-lite^2.0.02.6.0up to date
 lazy-regex^33.4.1up to date
 log^0.40.4.26up to date
 native-tls^0.20.2.14up to date
 pin-project^11.1.10up to date
 rustls ⚠️^0.230.23.23maybe insecure
 thiserror^22.0.12up to date

Dev dependencies

(7 total, 1 outdated)

CrateRequiredLatestStatus
 async-attributes^1.1.21.1.2up to date
 env_logger^0.110.11.6up to date
 pretty_assertions^1.0.01.4.1up to date
 rand^0.8.40.9.0out of date
 serial_test^3.03.2.0up to date
 testcontainers^0.230.23.3up to date
 webpki-roots^0.260.26.8up 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 network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.