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 exonum-testkit

Dependencies

(20 total, 6 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 actix^0.9.00.13.3out of date
 actix-web^2.0.04.5.1out of date
 chrono ⚠️^0.4.60.4.37maybe insecure
 exonum^1.0.01.0.0up to date
 exonum-api^1.0.01.0.0up to date
 exonum-derive^1.0.01.0.0up to date
 exonum-explorer^1.0.01.0.0up to date
 exonum-merkledb^1.0.01.0.0up to date
 exonum-node^1.0.01.0.0up to date
 exonum-proto^1.0.01.0.0up to date
 exonum-rust-runtime^1.0.01.0.0up to date
 futures^0.3.40.3.30up to date
 log^0.4.60.4.21up to date
 protobuf^2.11.03.4.0out of date
 reqwest^0.10.20.12.2out of date
 serde^1.0.101.0.197up to date
 serde_derive^1.01.0.197up to date
 serde_json^1.01.0.115up to date
 serde_urlencoded^0.6.00.7.1out of date
 tokio ⚠️^0.2.131.37.0out of date

Dev dependencies

(6 total, 2 outdated)

CrateRequiredLatestStatus
 assert_matches^1.2.01.5.0up to date
 bincode^1.2.11.3.3up to date
 hex^0.4.00.4.3up to date
 lazy_static^1.0.01.4.0up to date
 pretty_assertions^0.6.11.4.0out of date
 rand^0.70.8.5out of date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

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.