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.890.1.89up to date
 bitflags^2.11.12.12.1up to date
 bytes^1.11.11.11.1up to date
 chrono^0.4.440.4.44up to date
 dashmap^6.1.06.2.1up to date
 gloo-timers^0.4.00.4.0up to date
 log^0.4.290.4.31up to date
 serde^1.0.2281.0.228up to date
 serde_bytes^0.11.190.11.19up to date
 thiserror^2.0.182.0.18up to date
 tokio ⚠️^11.52.3maybe insecure
 tokio-util^0.7.180.7.18up to date
 wasm-bindgen-futures^0.4.710.4.72up to date

Dev dependencies

(6 total, all up-to-date)

CrateRequiredLatestStatus
 anyhow^1.0.1021.0.102up to date
 criterion^0.8.20.8.2up to date
 env_logger^0.11.100.11.10up to date
 futures^0.3.320.3.32up to date
 rand^0.10.10.10.1up to date
 russh^0.61.00.61.1up to 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);