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-time(8 total, 3 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| chrono ⚠️ | ^0.4.6 | 0.4.38 | maybe insecure |
| exonum | ^0.11.0 | 1.0.0 | out of date |
| exonum-derive | ^0.11.0 | 1.0.0 | out of date |
| failure | ^0.1.5 | 0.1.8 | up to date |
| protobuf ⚠️ | ^2.4.0 | 3.4.0 | out of date |
| serde | ^1.0.10 | 1.0.197 | up to date |
| serde_derive | ^1.0.10 | 1.0.197 | up to date |
| serde_json | ^1.0.2 | 1.0.116 | up to date |
(2 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| exonum-testkit | ^0.11.0 | 1.0.0 | out of date |
| pretty_assertions | ^0.6.1 | 1.4.0 | out of 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.