RustSec logo

History ⋅ Edit ⋅ JSON (OSV)

RUSTSEC-2026-0549

NSEC3 NODATA at a zone apex accepted without an NSEC3 record matching the query name (hickory-proto)

Reported
Issued
Package
hickory-proto (crates.io)
Type
Vulnerability
Categories
Keywords
#dns #dnssec #nsec3
Aliases
References
Patched
no patched versions
Unaffected
  • <0.25.0-alpha.3
  • >=0.26.0-beta.1

Description

In hickory-proto 0.25.0-alpha.3 through 0.26.0-alpha.1, NSEC3 NODATA validation returned a secure result for a query at the zone apex even when no NSEC3 record in the response matched the hash of the query name, which RFC 5155 section 8.5 requires. Someone who can answer or modify DNS responses could replay any genuine signed NSEC3 record from the zone with the zone's signed SOA record and get a denial of any record type at the apex accepted as secure.

From 0.26.0-beta.1 the DNSSEC validation code lives in the hickory-net crate, where this was fixed in hickory-net 0.26.2. No hickory-proto release contains a fix. Users of DNSSEC validation in hickory-proto 0.25 or 0.26.0-alpha.1 (directly or through hickory-resolver or hickory-recursor) should move to the 0.26.2 or later releases, which validate through hickory-net.

Advisory available under CC0-1.0 license.