GHSA-6w6g-hm98-mhgm
hickory-resolver: Unbounded TC-retry loop in `NameServerPool::try_send` (resource-exhaustion DoS)
Impact
When the `hickory-resolver` name server pool implementation receives an upstream response with the TC (truncated) header bit set, it re-queues the request to the same nameserver to retry with UDP transport disabled. However, the retry arm never inspects the transport that just answered and carries no iteration counter. An authoritative server that sets `TC=1` on **every** available transport keeps the resolver spinning on one persistent TCP connection until the 5s per-request wall-clock deadline expires. ### Reporter Qifan Zhang, Palo Alto Networks
An attacker can exploit this over the network, without logging in, without any action by a user. If it succeeds: high risk of outages.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| rust | hickory-resolver | >= 0.26.0-beta.1, < 0.26.2 | 0.26.2 |
Weakness classification
References
- GitHub advisory
- https://github.com/advisories/GHSA-6w6g-hm98-mhgm
- https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-6w6g-hm98-mhgm
- https://github.com/hickory-dns/hickory-dns/pull/3871
- https://github.com/hickory-dns/hickory-dns/commit/0848d2e9e4183499343318a690d6dd5e48bc21c1
- https://github.com/hickory-dns/hickory-dns/commit/5d37e2e04a36a87013a213b58b820345ef76a263
- https://github.com/hickory-dns/hickory-dns/releases/tag/v0.26.2