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.
stderrlog(5 total, 2 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| atty | ^0.2, <=0.2.11 | 0.2.14 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| log | ^0.4.1 | 0.4.21 | up to date |
| termcolor | ^1.0 | 1.4.1 | up to date |
| thread_local ⚠️ | ^0.3, <=0.3.4 | 1.1.8 | out of date |
(5 total, 3 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| clap | ~2.22.0 | 4.5.4 | out of date |
| docopt | ^0.6 | 1.1.1 | out of date |
| libc | ^0.2 | 0.2.153 | up to date |
| rustc-serialize ⚠️ | ^0.3 | 0.3.25 | insecure |
| structopt | ^0.2 | 0.3.26 | 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.
rustc-serialize: Stack overflow in rustc_serialize when parsing deeply nested JSONWhen parsing JSON using json::Json::from_str, there is no limit to the depth of the stack, therefore deeply nested objects can cause a stack overflow, which aborts the process.
Example code that triggers the vulnerability is
fn main() {
let _ = rustc_serialize::json::Json::from_str(&"[0,[".repeat(10000));
}
serde is recommended as a replacement to rustc_serialize.
thread_local: Data race in `Iter` and `IterMut`In the affected version of this crate, {Iter, IterMut}::next used a weaker memory ordering when loading values than what was required, exposing a potential data race
when iterating over a ThreadLocal's values.
Crates using Iter::next, or IterMut::next are affected by this issue.