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 tox

Dependencies

(12 total, 7 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 byteorder^11.5.0up to date
 bytes^0.41.6.0out of date
 cookie-factory^0.2.30.3.3out of date
 failure^0.10.1.8up to date
 futures^0.10.3.30out of date
 get_if_addrs^0.5.30.5.3up to date
 log^0.40.4.21up to date
 nom^3.2.17.1.3out of date
 parking_lot^0.60.12.1out of date
 sodiumoxide ⚠️^0.0.160.2.7out of date
 tokio ⚠️^0.1.71.37.0out of date
 tokio-codec^0.10.1.2up to date

Dev dependencies

(6 total, 4 outdated)

CrateRequiredLatestStatus
 env_logger^0.50.11.3out of date
 hex^0.30.4.3out of date
 quickcheck^0.61.0.3out of date
 rand^0.40.8.5out of date
 tokio-executor^0.10.1.10up to date
 tokio-timer^0.20.2.13up to date

Security Vulnerabilities

sodiumoxide: generichash::Digest::eq always return true

RUSTSEC-2019-0026

PartialEq implementation for generichash::Digest has compared itself to itself.

Digest::eq always returns true and Digest::ne always returns false.

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.