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.
bita(14 total, 7 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| atty | ^0.2.11 | 0.2.14 | up to date |
| blake2 | ^0.8.0 | 0.10.6 | out of date |
| chrono ⚠️ | ^0.4.6 | 0.4.41 | maybe insecure |
| clap | ^2.32.0 | 4.5.41 | out of date |
| crossbeam-channel | ^0.3.8 | 0.5.15 | out of date |
| curl | ^0.4.20 | 0.4.48 | up to date |
| error-chain | ^0.12.0 | 0.12.4 | up to date |
| fern | ^0.5.8 | 0.7.1 | out of date |
| log | ^0.4.6 | 0.4.27 | up to date |
| num_cpus | ^1.9.0 | 1.17.0 | up to date |
| protobuf ⚠️ | ^2.4.2 | 3.7.2 | out of date |
| rust-lzma | ^0.4.0 | 0.6.0 | out of date |
| threadpool | ^1.7.1 | 1.8.1 | up to date |
| zstd | ^0.4.22 | 0.13.3 | out of 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.
protobuf: Crash due to uncontrolled recursion in protobuf crateAffected 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.