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

(12 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix-web^0.7.184.5.1out of date
 exonum^0.11.01.0.0out of date
 failure^0.1.50.1.8up to date
 futures^0.1.250.3.30out of date
 log^0.4.60.4.21up to date
 protobuf ⚠️^2.4.03.4.0out of date
 reqwest^0.9.80.12.4out of date
 serde^1.0.101.0.199up to date
 serde_derive^1.0.101.0.199up to date
 serde_json^1.0.21.0.116up to date
 serde_urlencoded^0.5.40.7.1out of date
 tokio-core^0.1.170.1.18up to date

Dev dependencies

(7 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 assert_matches^1.2.01.5.0up to date
 exonum-derive^0.11.01.0.0out of date
 hex^0.3.20.4.3out of date
 lazy_static^1.0.01.4.0up to date
 pretty_assertions^0.6.11.4.0out of date
 rand^0.6.40.8.5out of date
 thread_local ⚠️^0.3.61.1.8out of date

Security Vulnerabilities

protobuf: Out of Memory in stream::read_raw_bytes_into()

RUSTSEC-2019-0003

Affected versions of this crate called Vec::reserve() on user-supplied input.

This allows an attacker to cause an Out of Memory condition while calling the vulnerable method on untrusted data.

thread_local: Data race in `Iter` and `IterMut`

RUSTSEC-2022-0006

In the affected version of this crate, {Iter, IterMut}::next used a weaker memory ordering when loading values than what was required, exposing a potential data race when iterating over a ThreadLocal's values.

Crates using Iter::next, or IterMut::next are affected by this issue.