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 thrussh-keys

Dependencies

(16 total, 10 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 base64^0.90.22.0out of date
 bit-vec^0.40.6.3out of date
 byteorder^1.21.5.0up to date
 cryptovec^0.40.6.1out of date
 dirs^1.05.0.1out of date
 futures^0.10.3.30out of date
 hex^0.30.4.3out of date
 log^0.40.4.21up to date
 num-bigint^0.10.4.4out of date
 num-integer^0.10.1.46up to date
 openssl ⚠️^0.100.10.64maybe insecure
 serde^1.01.0.199up to date
 serde_derive^1.01.0.199up to date
 thrussh-libsodium^0.10.3.0out of date
 tokio ⚠️^0.11.37.0out of date
 yasna^0.10.5.2out of date

Dev dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 env_logger^0.40.11.3out of date
 tempdir^0.30.3.7up to date
 tokio-uds^0.20.2.7up to date

Security Vulnerabilities

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.