This project contains known security vulnerabilities. Find detailed information at the bottom.
exonum(41 total, 24 outdated, 4 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix | ^0.7.9 | 0.13.5 | out of date |
| actix-net | ^0.2.6 | 0.2.6 | up to date |
| actix-web ⚠️ | ^0.7.18 | 4.15.0 | insecure |
| atty | ^0.2.11 | 0.2.14 | up to date |
| bit-vec | ^0.5.0 | 0.10.1 | out of date |
| byteorder | ^1.2.7 | 1.5.0 | up to date |
| bytes | ^0.4.11 | 1.12.1 | out of date |
| chrono | ^0.4.6 | 0.4.45 | up to date |
| clap | ^2.31.2 | 4.6.7 | out of date |
| ctrlc | ^3.1.1 | 3.5.2 | up to date |
| env_logger | ^0.6.0 | 0.11.11 | out of date |
| erased-serde | ^0.3 | 0.4.10 | out of date |
| exonum-crypto | ^0.11.0 | 1.0.0 | out of date |
| exonum-derive | ^0.11.0 | 1.0.0 | out of date |
| exonum_rocksdb | ^0.7.4 | 0.7.6 | up to date |
| exonum_sodiumoxide | ^0.0.21 | 0.0.24 | out of date |
| failure | ^0.1.5 | 0.1.8 | up to date |
| futures | ^0.1.25 | 0.3.34 | out of date |
| hex | ^0.3.2 | 0.4.3 | out of date |
| log | ^0.4.6 | 0.4.34 | up to date |
| os_info | ^1.0.1 | 3.15.0 | out of date |
| protobuf ⚠️ | ^2.4.0 | 3.7.2 | insecure |
| rand | ^0.6.4 | 0.10.3 | out of date |
| rand_xorshift | ^0.1.1 | 0.5.0 | out of date |
| rpassword | ^2.1.0 | 7.5.4 | out of date |
| rust_decimal | ^0.11.2 | 1.43.0 | out of date |
| serde | ^1.0.10 | 1.0.229 | up to date |
| serde_derive | ^1.0.64 | 1.0.229 | up to date |
| serde_json | ^1.0.19 | 1.0.151 | up to date |
| snow ⚠️ | ^0.5.2 | 0.10.0 | insecure |
| tokio ⚠️ | ^0.1.14 | 1.53.1 | insecure |
| tokio-codec | ^0.1.1 | 0.1.2 | up to date |
| tokio-core | ^0.1.17 | 0.1.18 | up to date |
| tokio-current-thread | ^0.1.4 | 0.1.7 | up to date |
| tokio-dns-unofficial | ^0.4.0 | 0.4.0 | up to date |
| tokio-io | ^0.1.11 | 0.1.13 | up to date |
| tokio-retry | ^0.2.0 | 0.3.2 | out of date |
| tokio-threadpool | ^0.1.10 | 0.1.18 | up to date |
| toml | ^0.4.10 | 1.1.6+spec-1.1.0 | out of date |
| uuid | ^0.7.1 | 1.26.1 | out of date |
| zeroize | ^0.5.2 | 1.9.0 | out of date |
(7 total, 4 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.2.8 | 0.8.2 | out of date |
| lazy_static | ^1.0.1 | 1.5.0 | up to date |
| modifier | ^0.1.0 | 0.1.0 | up to date |
| num | ^0.2.0 | 0.4.3 | out of date |
| pretty_assertions | ^0.6.1 | 1.4.1 | out of date |
| proptest | ^0.9.1 | 1.11.0 | out of date |
| tempdir | ^0.3.7 | 0.3.7 | up to 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.
tokio: Data race when sending and receiving after closing a `oneshot` channelIf 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.
snow: Unauthenticated Nonce Increment in snowThere was a logic bug where unauthenticated payloads could still cause a nonce increment in snow's internal state. For an attacker with privileges to inject packets into the channel over which the Noise session operates, this could allow a denial-of-service attack which could prevent message delivery by sending garbage data.
Note that this only affects those who are using the stateful TransportState, not those using StatelessTransportState.
This has been patched in version 0.9.5, and all users are recommended to update.
protobuf: Crash due to uncontrolled recursion in protobuf crateAffected version of this crate did not properly parse unknown fields when parsing a user-supplied input.
This allows an attacker to cause a stack overflow when parsing the mssage on untrusted data.