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.
exonum 0.10.3
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
(39 total, 22 outdated, 4 possibly insecure)
Crate | Required | Latest | Status |
---|---|---|---|
actix | ^0.7.9 | 0.13.3 | out of date |
actix-net | ^0.2.6 | 0.2.6 | up to date |
actix-web | ^0.7.18 | 4.5.1 | out of date |
atty | ^0.2.11 | 0.2.14 | up to date |
bit-vec | ^0.5.0 | 0.6.3 | out of date |
byteorder | ^1.2.7 | 1.5.0 | up to date |
bytes | ^0.4.11 | 1.6.0 | out of date |
chrono ⚠️ | ^0.4.6 | 0.4.37 | maybe insecure |
clap | ^2.31.2 | 4.5.4 | out of date |
ctrlc | ^3.1.1 | 3.4.4 | up to date |
env_logger | ^0.6.0 | 0.11.3 | out of date |
erased-serde | ^0.3 | 0.4.4 | out of date |
exonum-crypto | ^0.10.4 | 1.0.0 | out of date |
exonum-derive | ^0.10.0 | 1.0.0 | out of date |
exonum_rocksdb | ^0.7.4 | 0.7.6 | up to date |
exonum_sodiumoxide | ^0.0.20 | 0.0.24 | out of date |
failure | ^0.1.5 | 0.1.8 | up to date |
futures | ^0.1.25 | 0.3.30 | out of date |
hex | ^0.3.2 | 0.4.3 | out of date |
log | ^0.4.6 | 0.4.21 | up to date |
os_info | ^1.0.1 | 3.8.2 | out of date |
protobuf ⚠️ | ^2.2.0 | 3.4.0 | out of date |
rand | ^0.6.4 | 0.8.5 | out of date |
rand_xorshift | ^0.1.1 | 0.3.0 | out of date |
rust_decimal | ^0.10.2 | 1.35.0 | out of date |
serde | ^1.0.10 | 1.0.197 | up to date |
serde_derive | ^1.0.64 | 1.0.197 | up to date |
serde_json | ^1.0.19 | 1.0.115 | up to date |
snow ⚠️ | ^0.4.2 | 0.9.6 | out of date |
tokio ⚠️ | ^0.1.14 | 1.36.0 | out of date |
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.0 | out of date |
tokio-threadpool | ^0.1.10 | 0.1.18 | up to date |
toml | ^0.4.10 | 0.8.12 | out of date |
uuid | ^0.7.1 | 1.8.0 | out of date |
(7 total, 4 outdated)
Crate | Required | Latest | Status |
---|---|---|---|
criterion | ^0.2.8 | 0.5.1 | out of date |
lazy_static | ^1.0.1 | 1.4.0 | up to date |
modifier | ^0.1.0 | 0.1.0 | up to date |
num | ^0.2.0 | 0.4.1 | out of date |
pretty_assertions | ^0.5.1 | 1.4.0 | out of date |
proptest | ^0.8.7 | 1.4.0 | out of date |
tempdir | ^0.3.7 | 0.3.7 | up to date |
protobuf
: Out of Memory in stream::read_raw_bytes_into()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.
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.
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 await
ed 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 await
ed 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.