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

Dependencies

(39 total, 22 outdated, 4 possibly insecure)

CrateRequiredLatestStatus
 actix^0.7.90.13.3out of date
 actix-net^0.2.60.2.6up to date
 actix-web^0.7.184.5.1out of date
 atty^0.2.110.2.14up to date
 bit-vec^0.5.00.6.3out of date
 byteorder^1.2.71.5.0up to date
 bytes^0.4.111.6.0out of date
 chrono ⚠️^0.4.60.4.37maybe insecure
 clap^2.31.24.5.4out of date
 ctrlc^3.1.13.4.4up to date
 env_logger^0.6.00.11.3out of date
 erased-serde^0.30.4.4out of date
 exonum-crypto^0.10.41.0.0out of date
 exonum-derive^0.10.01.0.0out of date
 exonum_rocksdb^0.7.40.7.6up to date
 exonum_sodiumoxide^0.0.200.0.24out of date
 failure^0.1.50.1.8up to date
 futures^0.1.250.3.30out of date
 hex^0.3.20.4.3out of date
 log^0.4.60.4.21up to date
 os_info^1.0.13.8.2out of date
 protobuf ⚠️^2.2.03.4.0out of date
 rand^0.6.40.8.5out of date
 rand_xorshift^0.1.10.3.0out of date
 rust_decimal^0.10.21.35.0out of date
 serde^1.0.101.0.197up to date
 serde_derive^1.0.641.0.197up to date
 serde_json^1.0.191.0.115up to date
 snow ⚠️^0.4.20.9.6out of date
 tokio ⚠️^0.1.141.36.0out of date
 tokio-codec^0.1.10.1.2up to date
 tokio-core^0.1.170.1.18up to date
 tokio-current-thread^0.1.40.1.7up to date
 tokio-dns-unofficial^0.4.00.4.0up to date
 tokio-io^0.1.110.1.13up to date
 tokio-retry^0.2.00.3.0out of date
 tokio-threadpool^0.1.100.1.18up to date
 toml^0.4.100.8.12out of date
 uuid^0.7.11.8.0out of date

Dev dependencies

(7 total, 4 outdated)

CrateRequiredLatestStatus
 criterion^0.2.80.5.1out of date
 lazy_static^1.0.11.4.0up to date
 modifier^0.1.00.1.0up to date
 num^0.2.00.4.1out of date
 pretty_assertions^0.5.11.4.0out of date
 proptest^0.8.71.4.0out of date
 tempdir^0.3.70.3.7up to 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.

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If 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 snow

RUSTSEC-2024-0011

There 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.