Description
DNSSEC validation in Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 does not distinguish NODATA responses from wildcard-expanded positive responses. For a query that should return NODATA in a zone with wildcard records, an attacker can combine an NSEC3 record matching the query name with a signed wildcard record into a bogus positive response that validation accepts.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| hickory-dns | hickory-dns | 0.26.0-beta.1 – < 0.26.2, ≤ 0.26.0-alpha.1 | 0.26.2 |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | rust-hickory-net | 0.26.3-1 | — |
| Debian 14 | rust-hickory-proto | No fix yet | — |
| Debian 13 | rust-hickory-proto | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | rust-hickory-net +1 | No fix yet | — |
| Ubuntu 26.04 LTS | rust-hickory-proto | No fix yet | — |
| Ubuntu 24.04 LTS | rust-hickory-proto | No fix yet | — |