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-node(24 total, 9 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-rt | ^1.0.0 | 2.9.0 | out of date |
| anyhow | ^1.0.26 | 1.0.82 | up to date |
| async-trait | ^0.1.24 | 0.1.80 | up to date |
| bit-vec | ^0.6.0 | 0.6.3 | up to date |
| byteorder | ^1.2.7 | 1.5.0 | up to date |
| bytes | ^0.5.0 | 1.6.0 | out of date |
| chrono ⚠️ | ^0.4.6 | 0.4.38 | maybe insecure |
| exonum | ^1.0.0 | 1.0.0 | up to date |
| exonum-api | ^1.0.0 | 1.0.0 | up to date |
| exonum-derive | ^1.0.0 | 1.0.0 | up to date |
| exonum-merkledb | ^1.0.0 | 1.0.0 | up to date |
| exonum-proto | ^1.0.0 | 1.0.0 | up to date |
| exonum_sodiumoxide | ^0.0.23 | 0.0.24 | out of date |
| futures | ^0.3.4 | 0.3.30 | up to date |
| futures-retry | ^0.5.0 | 0.6.0 | out of date |
| log | ^0.4.6 | 0.4.21 | up to date |
| protobuf | ^2.8.1 | 3.4.0 | out of date |
| rand | ^0.7 | 0.8.5 | out of date |
| serde | ^1.0.101 | 1.0.199 | up to date |
| serde_derive | ^1.0.101 | 1.0.199 | up to date |
| snow ⚠️ | ^0.6.0 | 0.9.6 | out of date |
| thiserror | ^1.0 | 1.0.59 | up to date |
| tokio ⚠️ | ^0.2.13 | 1.37.0 | out of date |
| tokio-util | ^0.3.0 | 0.7.10 | out of date |
(10 total, 6 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bincode | ^1.2.1 | 1.3.3 | up to date |
| criterion | ^0.3.0 | 0.5.1 | out of date |
| exonum-rust-runtime | ^1.0.0 | 1.0.0 | up to date |
| hex | ^0.4.0 | 0.4.3 | up to date |
| nix ⚠️ | ^0.17.0 | 0.28.0 | out of date |
| pretty_assertions | ^0.6.1 | 1.4.0 | out of date |
| reqwest | ^0.10.2 | 0.12.4 | out of date |
| rusty-fork | ^0.2.2 | 0.3.0 | out of date |
| serde_json | ^1.0.44 | 1.0.116 | up to date |
| toml | ^0.5.6 | 0.8.12 | out of date |
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
No workarounds are known.
nix: Out-of-bounds write in nix::unistd::getgrouplistOn certain platforms, if a user has more than 16 groups, the
nix::unistd::getgrouplist function will call the libc getgrouplist
function with a length parameter greater than the size of the buffer it
provides, resulting in an out-of-bounds write and memory corruption.
The libc getgrouplist function takes an in/out parameter ngroups
specifying the size of the group buffer. When the buffer is too small to
hold all of the requested user's group memberships, some libc
implementations, including glibc and Solaris libc, will modify ngroups
to indicate the actual number of groups for the user, in addition to
returning an error. The version of nix::unistd::getgrouplist in nix
0.16.0 and up will resize the buffer to twice its size, but will not
read or modify the ngroups variable. Thus, if the user has more than
twice as many groups as the initial buffer size of 8, the next call to
getgrouplist will then write past the end of the buffer.
The issue would require editing /etc/groups to exploit, which is usually only editable by the root user.
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.