Deps.rs

nimiq-consensus 0.2.0

[![dependency status](https://deps.rs/crate/nimiq-consensus/0.2.0/status.svg)](https://deps.rs/crate/nimiq-consensus/0.2.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 nimiq-consensus

Dependencies

(20 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 beserial^0.20.2.0up to date
 failure^0.10.1.8up to date
 futures^0.10.3.30out of date
 log^0.40.4.21up to date
 nimiq-block^0.20.2.0up to date
 nimiq-blockchain^0.20.2.0up to date
 nimiq-collections^0.20.2.0up to date
 nimiq-database^0.20.2.0up to date
 nimiq-hash^0.20.2.0up to date
 nimiq-macros^0.20.2.0up to date
 nimiq-mempool^0.20.2.0up to date
 nimiq-messages^0.20.2.0up to date
 nimiq-network^0.20.2.0up to date
 nimiq-network-primitives^0.20.2.0up to date
 nimiq-transaction^0.20.2.0up to date
 nimiq-utils^0.20.2.0up to date
 parking_lot^0.70.12.2out of date
 rand^0.60.8.5out of date
 tokio ⚠️^0.11.37.0out of date
 weak-table^0.20.3.2out 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.