BOGUS configured primary hostname accepted for XFR in auth/rpz zones
NLnet Labs Unbound
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| NLnet Labs Unbound |
| No fix yet |
Original description
In NLnet Labs Unbound 1.7.0 up to and including 1.25.1, when an auth/rpz zone has a configured primary hostname that resolves to BOGUS A/AAAA, it is still considered as a possible XFR endpoint. A malicious actor that can spoof the hostname's A/AAAA record (no valid RRSIG required) becomes the zone's XFR primary and can replaces the entire zone/the resolver's entire response policy.
From the CVE record · NLnet Labs