mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-02-23 15:38:27 +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.
27 lines
834 B
Markdown
27 lines
834 B
Markdown
```toml
|
|
[advisory]
|
|
id = "RUSTSEC-2018-0007"
|
|
package = "trust-dns-proto"
|
|
aliases = ["CVE-2018-20994"]
|
|
date = "2018-10-09"
|
|
keywords = ["stack-overflow", "crash"]
|
|
|
|
[versions]
|
|
patched = [">= 0.4.3", ">= 0.5.0-alpha.3"]
|
|
```
|
|
|
|
# Stack overflow when parsing malicious DNS packet
|
|
|
|
There's a stack overflow leading to a crash when Trust-DNS's parses a
|
|
malicious DNS packet.
|
|
|
|
Affected versions of this crate did not properly handle parsing of DNS message
|
|
compression (RFC1035 section 4.1.4). The parser could be tricked into infinite
|
|
loop when a compression offset pointed back to the same domain name to be
|
|
parsed.
|
|
|
|
This allows an attacker to craft a malicious DNS packet which when consumed
|
|
with Trust-DNS could cause stack overflow and crash the affected software.
|
|
|
|
The flaw was corrected by trust-dns-proto 0.4.3 and upcoming 0.5.0 release.
|