Deps.rs

russh 0.46.0

[![dependency status](https://deps.rs/crate/russh/0.46.0/status.svg)](https://deps.rs/crate/russh/0.46.0)

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

Dependencies

(38 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 aes^0.80.8.4up to date
 aes-gcm^0.100.10.3up to date
 async-trait^0.10.1.83up to date
 bitflags^2.02.6.0up to date
 byteorder^1.41.5.0up to date
 cbc^0.10.1.2up to date
 chacha20^0.90.9.1up to date
 ctr^0.90.9.2up to date
 curve25519-dalek^4.1.34.1.3up to date
 des^0.8.10.8.1up to date
 digest^0.100.10.7up to date
 elliptic-curve^0.130.13.8up to date
 flate2^1.01.0.35up to date
 futures^0.30.3.31up to date
 generic-array^0.141.1.0out of date
 hex-literal^0.40.4.1up to date
 hmac^0.120.12.1up to date
 log^0.40.4.22up to date
 num-bigint^0.40.4.6up to date
 once_cell^1.131.20.2up to date
 openssl ⚠️^0.100.10.68maybe insecure
 p256^0.130.13.2up to date
 p384^0.130.13.0up to date
 p521^0.130.13.3up to date
 poly1305^0.80.8.0up to date
 rand^0.80.8.5up to date
 rand_core^0.6.40.6.4up to date
 russh-cryptovec^0.7.00.7.3up to date
 russh-keys^0.46.00.46.0up to date
 russh-sftp^2.0.52.0.6up to date
 russh-util^0.46.00.46.0up to date
 sha1^0.100.10.6up to date
 sha2^0.100.10.8up to date
 ssh-encoding^0.20.2.0up to date
 ssh-key^0.60.6.7up to date
 subtle^2.42.6.1up to date
 thiserror^1.02.0.3out of date
 tokio ⚠️^1.17.01.41.1maybe insecure

Dev dependencies

(9 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.93up to date
 clap^3.24.5.21out of date
 env_logger^0.110.11.5up to date
 rand^0.8.50.8.5up to date
 ratatui^0.26.00.29.0out of date
 shell-escape^0.10.1.5up to date
 termion^24.0.3out of date
 tokio ⚠️^1.17.01.41.1maybe insecure
 tokio-fd^0.30.3.0up 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);

openssl: `MemBio::get_buf` has undefined behavior with empty buffers

RUSTSEC-2024-0357

Previously, MemBio::get_buf called slice::from_raw_parts with a null-pointer, which violates the functions invariants, leading to undefined behavior. In debug builds this would produce an assertion failure. This is now fixed.