mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-01-21 19:08:09 +01:00
ac125ee29a
As proposed in #240 and tracked in #414, this PR translates all advisories into the new "V3" advisory format, which is based on Markdown with leading TOML front matter. This format makes it easier to see rendered Markdown syntax descriptions, whether rendered by an IDE or GitHub. This should help with both crafting advisories initially as well as review, and ideally encourages more lengthy descriptions. Support for this format shipped in `cargo-audit` v0.12.0 on May 6th, 2020.
32 lines
900 B
Markdown
32 lines
900 B
Markdown
```toml
|
|
[advisory]
|
|
id = "RUSTSEC-2018-0006"
|
|
package = "yaml-rust"
|
|
aliases = ["CVE-2018-20993"]
|
|
date = "2018-09-17"
|
|
keywords = ["crash"]
|
|
url = "https://github.com/chyh1990/yaml-rust/pull/109"
|
|
|
|
[versions]
|
|
patched = [">= 0.4.1"]
|
|
```
|
|
|
|
# Uncontrolled recursion leads to abort in deserialization
|
|
|
|
Affected 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:
|
|
|
|
1. The input to the YAML parser is always trusted - is included at compile
|
|
time via `include_str!`.
|
|
|
|
2. The nesting level is never deep enough to trigger the overflow in practice
|
|
(at most 5).
|