Deps.rs

lapin-futures-openssl 0.10.1

[![dependency status](https://deps.rs/crate/lapin-futures-openssl/0.10.1/status.svg)](https://deps.rs/crate/lapin-futures-openssl/0.10.1)

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 lapin-futures-openssl

Dependencies

(4 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.10.3.30out of date
 lapin-futures-tls-internal^0.7.10.7.1up to date
 openssl ⚠️^0.100.10.64maybe insecure
 tokio-openssl^0.30.6.4out of date

Dev dependencies

(3 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.60.11.3out of date
 failure^0.10.1.8up to date
 tokio ⚠️^0.1.61.37.0out of 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.