Hickory-dns hickory-resolver
hickory-resolver before 0.26.2 DNSSEC Validation Bypass
hickory-resolver versions before 0.26.2 fail to propagate bogus DNSSEC proof states through the Resolver::lookup() and Resolver::lookup_ip() APIs, allowing invalid records to be returned as successful results. Attackers controlling the answering zone or positioned on the network path can have forged DNS records accepted as validated, bypassing DNSSEC authentication checks.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.7high · scored by CNA · CWE-347
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
hickory-dns hickory-resolver
- < 0.26.2
Fixed in 0.26.2
Mitigation
Upgrade hickory-resolver to 0.26.2 or later.
References
- Vendor advisory github.com/hickory-dns/hickory-dns/security/ad…
- Patch github.com/hickory-dns/hickory-dns/commit/3072…
- Patch github.com/hickory-dns/hickory-dns/pull/3871
1 more
- Release notes github.com/hickory-dns/hickory-dns/releases/ta…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.