نسخههای متأثر
- نسخههای متأثر
- >=0.25.0-alpha.3
- نسخهٔ اصلاحشده
- اعلام نشده
- نسخههای متأثر
- >=0.26.0-beta.1 <0.26.2
- نسخهٔ اصلاحشده
- 0.26.2
بهرهبرداری
شرح آسیبپذیری
When a referral listed name servers outside the delegated zone and gave no glue addresses, the recursor looked up A and AAAA records for every listed name server, recursing into each one. Only the chain-depth limits applied. There was no cap on how many name servers it chased per referral or on the total upstream work per client query.
Someone who controls a zone can return referrals that list many glueless name servers in a victim's domain, and nest them, so that each client query makes the recursor send a large number of queries to the victim's servers (the NXNSAttack pattern). The same can exhaust the recursor's own resources.
This affects the recursive resolver, which is in hickory-resolver behind the opt-in recursor feature from 0.26.0-beta.1. Earlier releases shipped it as the separate hickory-recursor crate.
From 0.26.2 the recursor follows at most 5 glueless name servers per delegation and sends at most 200 upstream queries per client request.
پیوندها
- https://crates.io/crates/hickory-recursor
- https://crates.io/crates/hickory-resolver
- https://github.com/hickory-dns/hickory-dns/commit/47cd005b8f3d190134bbb943d2328ef8a83ade8c
- https://github.com/hickory-dns/hickory-dns/commit/74062f3a3ef6904b64717dd025945702b2cf4133
- https://rustsec.org/advisories/RUSTSEC-2026-0515.html
- https://rustsec.org/advisories/RUSTSEC-2026-0521.html

