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-crypto(13 total, 7 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| byteorder | ^1.2.7 | 1.5.0 | up to date |
| chrono ⚠️ | ^0.4.6 | 0.4.38 | maybe insecure |
| exonum_sodiumoxide | ^0.0.22 | 0.0.24 | out of date |
| hex | ^0.3.2 | 0.4.3 | out of date |
| hex-buffer-serde | ^0.2.0 | 0.4.0 | out of date |
| pwbox | ^0.2.0 | 0.5.0 | out of date |
| rand | ^0.7 | 0.8.5 | out of date |
| rust_decimal | ^1.0 | 1.35.0 | up to date |
| serde | ^1.0.10 | 1.0.198 | up to date |
| serde_derive | ^1.0.64 | 1.0.198 | up to date |
| serde_json | ^1.0.19 | 1.0.116 | up to date |
| toml | ^0.5.0 | 0.8.12 | out of date |
| uuid | ^0.7.1 | 1.8.0 | out of date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tempdir | ^0.3.7 | 0.3.7 | up to 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.