Hickory DNS denial of service in NSEC3 proof validation
hickory-dns
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| hickory-proto crates.io |
|
|
| hickory-net crates.io |
|
hickory-dns
| Product | Affected | Fixed in |
|---|---|---|
| hickory-proto crates.io |
|
|
| hickory-net crates.io |
|
0.26.1Hickory DNS hickory-proto 0.25.0-alpha.3 through 0.25.2 and hickory-net before 0.26.1 contain an unbounded loop vulnerability in DnssecDnsHandle NSEC3 closest-encloser proof validation when the SOA owner is not an ancestor of the QNAME. Upstream attackers can return NoData or NXDomain responses with a cross-zone SOA record to panic debug builds or exhaust memory in release builds.
From the CVE record · VulnCheck
An unbounded loop in DnssecDnsHandle NSEC3 closest-encloser proof validation affects hickory-proto and hickory-net. An upstream attacker can return a NoData or NXDomain response with a cross-zone SOA record, causing debug builds to panic or release builds to exhaust memory.
Engineers using hickory-proto 0.25.0-alpha.3 through 0.25.2 or hickory-net before 0.26.1 should check their deployments.