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 russh-sftp

Dependencies

(13 total, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.910.1.92up to date
 bitflags^2.13.12.13.1up to date
 bytes^1.12.11.12.1up to date
 chrono^0.4.450.4.45up to date
 dashmap^6.2.16.2.1up to date
 gloo-timers^0.4.00.4.0up to date
 log^0.4.330.4.34up to date
 serde^1.0.2291.0.229up to date
 serde_bytes^0.11.190.11.19up to date
 thiserror^2.0.192.0.20up to date
 tokio ⚠️^11.53.1maybe insecure
 tokio-util^0.7.190.7.19up to date
 wasm-bindgen-futures^0.4.760.4.77up to date

Dev dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.1041.0.104up to date
 criterion^0.8.20.8.2up to date
 env_logger^0.11.110.11.11up to date
 futures^0.3.330.3.34up to date
 rand^0.10.20.10.2up to date
 russh^0.62.50.63.1out of date

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