Hickory DNS recursor denial of service via bogus-answer caching
hickory-dns
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| hickory-dns hickory-dns |
| No fix yet |
| hickory-dns hickory-dns |
|
|
| hickory-dns hickory-dns |
|
|
hickory-dns
| Product | Affected | Fixed in |
|---|---|---|
| hickory-dns hickory-dns |
| No fix yet |
| hickory-dns hickory-dns |
|
|
| hickory-dns hickory-dns |
|
|
The validating recursor in Hickory DNS hickory-recursor 0.25.0 through 0.26.0-alpha.1, hickory-resolver 0.26.0-alpha.1 before 0.26.2, and hickory-net 0.26.0-beta.1 before 0.26.2 caches DNSSEC-bogus answers using the untrusted, attacker-supplied record TTL (capped at 24 hours) instead of a short validation-failure TTL. A remote attacker who spoofs a single authoritative response with an invalid signature and a long TTL can keep the bogus result cached for up to 24 hours.
From the CVE record · VulnCheck
The validating recursor caches DNSSEC-bogus answers using an attacker-supplied record TTL, capped at 24 hours, instead of a short validation-failure TTL. A remote attacker who spoofs one authoritative response with an invalid signature and a long TTL can keep the bogus result cached for up to 24 hours.
Check deployments using hickory-recursor 0.25.0 through 0.26.0-alpha.1, hickory-resolver 0.26.0-alpha.1 before 0.26.2, or hickory-net 0.26.0-beta.1 before 0.26.2.