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

(14 total, 3 possibly insecure)

CrateRequiredLatestStatus
 async-native-tls^0.60.6.0up to date
 async-trait^0.10.1.92up to date
 chrono ⚠️^0.40.4.45maybe insecure
 futures-rustls^0.260.26.0up to date
 lazy-regex^33.6.1up to date
 log^0.40.4.34up to date
 native-tls^0.20.2.18up to date
 pin-project^11.1.13up to date
 rustls ⚠️^0.230.23.44maybe insecure
 rustls-pki-types^11.15.1up to date
 smol^22.0.2up to date
 thiserror^22.0.20up to date
 tokio ⚠️^11.53.1maybe insecure
 tokio-rustls^0.260.26.5up to date

Dev dependencies

(5 total, 1 outdated)

CrateRequiredLatestStatus
 env_logger^0.110.11.11up to date
 pretty_assertions^11.4.1up to date
 rand^0.100.10.2up to date
 testcontainers^0.270.28.0out of date
 webpki-roots^11.0.9up 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

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);

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.