Deps.rs

russh 0.61.2

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

This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate russh

Dependencies

(69 total, 12 outdated, 1 insecure)

CrateRequiredLatestStatus
 aes^0.90.9.3up to date
 async-trait^0.1.500.1.92up to date
 aws-lc-rs^1.16.21.18.2up to date
 bitflags^2.02.13.2up to date
 block-padding^0.40.4.2up to date
 byteorder^1.41.5.0up to date
 bytes^1.71.12.1up to date
 cbc^0.20.2.1up to date
 cipher^0.5.10.5.2up to date
 criterion^0.70.8.2out of date
 crypto-bigint^0.7.30.7.5up to date
 ctr^0.100.10.1up to date
 curve25519-dalek=5.0.0-rc.05.0.0out of date
 data-encoding^2.32.11.1up to date
 delegate^0.130.13.5up to date
 der^0.80.8.2up to date
 des^0.90.9.0up to date
 digest^0.11.0-rc.50.11.3up to date
 ecdsa=0.17.0-rc.180.17.0out of date
 ed25519-dalek=3.0.0-rc.03.0.0out of date
 elliptic-curve=0.14.0-rc.330.14.1out of date
 enum_dispatch^0.3.130.3.13up to date
 flate2^1.0.151.1.10up to date
 futures^0.30.3.34up to date
 generic-array^1.3.31.4.5up to date
 getrandom^0.40.4.3up to date
 ghash^0.6.00.6.0up to date
 hex-literal^11.1.0up to date
 hmac^0.130.13.0up to date
 inout^0.20.2.2up to date
 keccak^0.2.00.2.2up to date
 log^0.4.110.4.34up to date
 md5^0.80.8.1up to date
 ml-kem^0.30.3.2up to date
 module-lattice^0.20.2.3up to date
 internal-russh-num-bigint=0.5.00.5.0up to date
 num-bigint^0.4.60.5.1out of date
 p256=0.14.0-rc.100.14.0out of date
 p384=0.14.0-rc.100.14.0out of date
 p521=0.14.0-rc.100.14.0out of date
 pageant^0.20.2.4up to date
 pbkdf2^0.130.13.0up to date
 pkcs1=0.8.0-rc.40.7.5up to date
 pkcs5^0.80.8.1up to date
 pkcs8^0.110.11.0up to date
 polyval^0.7.10.7.3up to date
 rand^0.100.10.3up to date
 rand_core^0.10.00.10.1up to date
 ring^0.17.140.17.14up to date
 rsa ⚠️=0.10.0-rc.180.9.10insecure
 russh-cryptovec^0.61.00.62.0out of date
 russh-util^0.52.00.52.0up to date
 salsa20^0.11.00.11.0up to date
 scrypt^0.12.00.12.0up to date
 sec1^0.80.8.1up to date
 sha1^0.110.11.0up to date
 sha2^0.110.11.1up to date
 sha3^0.11.00.12.0out of date
 signature^3.0.0-rc.103.0.0up to date
 spki^0.80.8.1up to date
 ssh-encoding=0.3.0-rc.90.3.0out of date
 ssh-key=0.7.0-rc.100.6.7up to date
 subtle^2.42.6.1up to date
 thiserror^2.0.182.0.21up to date
 tokio^1.17.01.53.3up to date
 typenum^1.171.20.1up to date
 universal-hash^0.6.10.6.1up to date
 yasna^0.60.6.0up to date
 zeroize^1.71.9.1up to date

Dev dependencies

(12 total, 1 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.41.0.104up to date
 clap^44.6.7up to date
 env_logger^0.110.11.11up to date
 rand^0.100.10.3up to date
 ratatui^0.300.30.2up to date
 russh-sftp^2.1.03.0.1out of date
 shell-escape^0.10.1.5up to date
 tempfile^3.14.03.27.0up to date
 termion^44.0.6up to date
 tokio^1.17.01.53.3up to date
 tokio-fd^0.30.3.0up to date
 tokio-stream^0.1.30.1.19up to date

Security Vulnerabilities

rsa: Marvin Attack: potential key recovery through timing sidechannels

RUSTSEC-2023-0071

Impact

Due to a non-constant-time implementation, information about the private key is leaked through timing information which is observable over the network. An attacker may be able to use that information to recover the key.

Patches

No patch is yet available. The crypto-bigint migration (RustCrypto/RSA#394) did not close this. Tracking is RustCrypto/RSA#626 (padding still not constant-time). Implicit rejection work is in RustCrypto/RSA#680; default-path blinding is in RustCrypto/RSA#702.

Still affected as of 2026-09-12: rsa 0.9.10 (latest stable) and rsa 0.10.0-rc.18 (latest). patched = [] is intentional.

Workarounds

Avoid using the rsa crate in settings where attackers can observe timing, for example over the network. Local use on a non-compromised computer is fine.

References

This vulnerability was discovered as part of the "Marvin Attack", which revealed several implementations of RSA including OpenSSL had not properly mitigated timing sidechannel attacks.