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 openssh-sftp-client

Dependencies

(13 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.2.11.10.1up to date
 derive_destructure2^0.1.00.1.3up to date
 futures-core^0.3.280.3.31up to date
 once_cell^1.9.01.21.3up to date
 openssh^0.10.00.11.5out of date
 openssh-sftp-client-lowlevel^0.6.00.7.1out of date
 openssh-sftp-error^0.4.00.5.1out of date
 pin-project^1.0.101.1.10up to date
 scopeguard^1.1.01.2.0up to date
 tokio ⚠️^1.11.01.46.0maybe insecure
 tokio-io-utility^0.7.40.7.6up to date
 tokio-util^0.7.80.7.15up to date
 tracing^0.1.370.1.41up to date

Dev dependencies

(5 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-util^0.3.280.3.31up to date
 openssh^0.10.00.11.5out of date
 pretty_assertions^1.1.01.4.1up to date
 tempfile^3.1.03.20.0up to date
 tokio ⚠️^1.11.01.46.0maybe insecure

Security Vulnerabilities

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);