Deps.rs

yskszk63 / ssssh

[![dependency status](https://deps.rs/repo/github/yskszk63/ssssh/status.svg)](https://deps.rs/repo/github/yskszk63/ssssh)

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

Crate ssssh

Dependencies

(15 total, 5 outdated, 1 insecure)

CrateRequiredLatestStatus
 futures^0.30.3.34up to date
 bytes^1.01.12.1up to date
 thiserror^1.02.0.21out of date
 ring ⚠️^0.160.17.14insecure
 log^0.40.4.35up to date
 getset^0.10.1.7up to date
 derive-new^0.50.7.0out of date
 derive_builder^0.100.20.2out of date
 linked-hash-map^0.50.5.6up to date
 base64^0.130.23.1out of date
 tokio-pipe^0.20.2.12up to date
 authorized_keys^1.0.01.0.0up to date
 tokio^1.41.54.1up to date
 tokio-stream^0.10.1.19up to date
 openssl^0.100.10.82up to date

Dev dependencies

(8 total, 4 outdated)

CrateRequiredLatestStatus
 env_logger^0.80.11.11out of date
 anyhow^1.01.0.104up to date
 ssh2^0.90.9.7up to date
 libssh2-sys^0.20.3.4out of date
 nix^0.200.31.3out of date
 simple_logger^1.65.2.0out of date
 tokio-test^0.40.4.6up to date
 tokio^1.41.54.1up to date

Security Vulnerabilities

ring: Some AES functions may panic when overflow checking is enabled.

RUSTSEC-2025-0009

ring::aead::quic::HeaderProtectionKey::new_mask() may panic when overflow checking is enabled. In the QUIC protocol, an attacker can induce this panic by sending a specially-crafted packet. Even unintentionally it is likely to occur in 1 out of every 2**32 packets sent and/or received.

On 64-bit targets operations using ring::aead::{AES_128_GCM, AES_256_GCM} may panic when overflow checking is enabled, when encrypting/decrypting approximately 68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols like TLS and SSH are not affected by this because those protocols break large amounts of data into small chunks. Similarly, most applications will not attempt to encrypt/decrypt 64GB of data in one chunk.

Overflow checking is not enabled in release mode by default, but RUSTFLAGS="-C overflow-checks" or overflow-checks = true in the Cargo.toml profile can override this. Overflow checking is usually enabled by default in debug mode.