Affected 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.
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.
yaml-merge-keys(5 total, 3 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| error-chain | >=0.9, <0.11 | 0.12.4 | out of date |
| itertools | ~0.7 | 0.12.1 | out of date |
| lazy_static | ^1.0 | 1.4.0 | up to date |
| serde_yaml ⚠️ | ~0.8 | 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).