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.
exonum-testkit(11 total, 5 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-web ⚠️ | ^0.6.15 | 4.5.1 | out of date |
| exonum | ^0.9.7 | 1.0.0 | out of date |
| failure | ^0.1.2 | 0.1.8 | up to date |
| futures | ^0.1.23 | 0.3.30 | out of date |
| log | ^0.4.3 | 0.4.21 | up to date |
| reqwest | ^0.8.6 | 0.12.4 | out of date |
| serde | ^1.0.10 | 1.0.200 | up to date |
| serde_derive | ^1.0.10 | 1.0.200 | up to date |
| serde_json | ^1.0.2 | 1.0.116 | up to date |
| serde_urlencoded | ^0.5.2 | 0.7.1 | out of date |
| tokio-core | ^0.1.17 | 0.1.18 | up to date |
(5 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| assert_matches | ^1.2.0 | 1.5.0 | up to date |
| lazy_static | ^1.0.0 | 1.4.0 | up to date |
| pretty_assertions | ^0.5.1 | 1.4.0 | out of date |
| rand | ^0.4.2 | 0.8.5 | out of date |
| thread_local ⚠️ | ^0.3.5 | 1.1.8 | out of date |
actix-web: Multiple memory safety issuesAffected versions contain multiple memory safety issues, such as:
Send marker trait to objects that cannot be safely sent between threadsThis may result in a variety of memory corruption scenarios, most likely use-after-free.
A significant refactoring effort has been conducted to resolve these issues.
thread_local: Data race in `Iter` and `IterMut`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.