`Resolver::lookup` and `lookup_ip` returned records that failed DNSSEC validation
Historical advisory saved 12 Nov 2026 15:18:33 UTC. The publisher may have updated it since then. Latest advisory.
osv · RUSTSEC-2026-0514
PublishedWith DNSSEC validation enabled, `Resolver::lookup()` and `Resolver::lookup_ip()` returned `Ok` with the records even when validation found the response bogus. The result was only visible in each record's proof status, which callers had to inspect themselves. Applications that enable validation and treat a successful lookup as validated data would therefore accept forged or tampered answers from anyone who can answer or modify their DNS traffic. From 0.26.2 a lookup whose records are bogus fails with a "DNSSEC validation failed" error (`DnsError::DnssecBogus`), the error is not retried, and the hickory-server forwarder answers SERVFAIL for it.
- Source published
- 3 Sep 2026 12:00:00 UTC
- Source modified
- 12 Nov 2026 14:30:06 UTC
- Saved here
- 12 Nov 2026 15:18:33 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N