Hickory DNS access control bypass via IPv4-mapped IPv6 addresses
hickory-dns
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| hickory-dns hickory-dns |
| No fix yet |
| hickory-dns hickory-dns |
|
|
| hickory-dns hickory-dns |
|
|
hickory-dns
| Product | Affected | Fixed in |
|---|---|---|
| hickory-dns hickory-dns |
| No fix yet |
| hickory-dns hickory-dns |
|
|
| hickory-dns hickory-dns |
|
|
| hickory-dns hickory-dns |
|
|
hickory-proto and hickory-resolver 0.26.0 before 0.26.2, hickory-server 0.25.0-alpha.1 before 0.26.2, and hickory-recursor 0.25.0-alpha.3 through 0.26.0-alpha.1 fail to canonicalize IPv4-mapped IPv6 addresses when checking deny_answers, deny_server, or AccessControlSet rules. Attackers can use IPv4-mapped addresses to evade answer filtering, trigger queries to denied nameservers, or reach hickory-server library deployments on dual-stack IPv6 sockets from denied clients.
From the CVE record · VulnCheck
Affected hickory-dns packages do not canonicalize IPv4-mapped IPv6 addresses when checking deny_answers, deny_server, or AccessControlSet rules. Attackers can use those addresses to evade answer filtering or cause queries to denied nameservers. In hickory-server library deployments using dual-stack IPv6 sockets, denied clients can also reach the server.
Check deployments using hickory-proto or hickory-resolver 0.26.0 through versions before 0.26.2, hickory-server 0.25.0-alpha.1 through versions before 0.26.2, or hickory-recursor 0.25.0-alpha.3 through 0.26.0-alpha.1.