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

(18 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.261.0.102up to date
 chrono ⚠️^0.4.60.4.44maybe insecure
 env_logger^0.7.10.11.10out of date
 exonum-crypto^1.0.01.0.0up to date
 exonum-derive^1.0.01.0.0up to date
 exonum-keys^1.0.01.0.0up to date
 exonum-merkledb^1.0.01.0.0up to date
 exonum-proto^1.0.01.0.0up to date
 futures^0.3.40.3.32up to date
 hex^0.4.00.4.3up to date
 log^0.4.60.4.29up to date
 os_info^2.03.14.0out of date
 protobuf ⚠️^2.8.13.7.2out of date
 semver^0.9.01.0.28out of date
 serde^1.0.1011.0.228up to date
 serde_derive^1.0.1011.0.228up to date
 serde_str^0.1.00.1.0up to date
 thiserror^1.02.0.18out of date

Dev dependencies

(6 total, 4 outdated)

CrateRequiredLatestStatus
 assert_matches^1.3.01.5.0up to date
 bincode^1.2.03.0.0out of date
 bit-vec^0.6.00.9.1out of date
 criterion^0.3.00.8.2out of date
 pretty_assertions^0.6.11.4.1out of date
 serde_json^1.0.191.0.149up to date

Security Vulnerabilities

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

protobuf: Crash due to uncontrolled recursion in protobuf crate

RUSTSEC-2024-0437

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