This project contains known security vulnerabilities. Find detailed information at the bottom.
treediff(4 total, 1 outdated, 1 insecure, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| rustc-serialize ⚠️ | ^0.3.22 | 0.3.25 | insecure |
| serde_json | ^1.0.2 | 1.0.145 | up to date |
| serde_yaml ⚠️ | ^0.7 | 0.9.34+deprecated | out of date |
| yaml-rust ⚠️ | ^0.4 | 0.4.5 | maybe insecure |
serde_yaml: Uncontrolled recursion leads to abort in deserializationAffected versions of this crate did not properly check for recursion while deserializing aliases.
This allows an attacker to make a YAML file with an alias referring to itself causing an abort.
The flaw was corrected by checking the recursion depth.
yaml-rust: Uncontrolled recursion leads to abort in deserializationAffected versions of this crate did not prevent deep recursion while deserializing data structures.
This allows an attacker to make a YAML file with deeply nested structures that causes an abort while deserializing it.
The flaw was corrected by checking the recursion depth.
Note: clap 2.33 is not affected by this because it uses yaml-rust
in a way that doesn't trigger the vulnerability. More specifically:
The input to the YAML parser is always trusted - is included at compile
time via include_str!.
The nesting level is never deep enough to trigger the overflow in practice (at most 5).
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.