A denial of service flaw was found in the way BIND handled query responses when both DNS64 and RPZ were used. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure or a null pointer dereference via a specially crafted DNS response.
As per upstream advisory:
Under some conditions when using both DNS64 and RPZ to rewrite query responses, query processing can resume in an inconsistent state leading to either an INSIST assertion failure or an attempt to read through a NULL pointer.
Servers utilizing both DNS64 and RPZ are potentially susceptible to encountering this condition. When this condition occurs, it will result in either an INSIST assertion failure (and subsequent abort) or an attempt to read through a NULL pointer. On most platforms a NULL pointer read leads to a segmentation fault (SEGFAULT), which causes the process to be terminated.
Only servers which are configured to simultaneously use both Response Policy Zones (RPZ) and DNS64 (a method for synthesizing AAAA records from A records) can be affected by this vulnerability.
While it is possible to avoid the condition by removing either DNS64 or RPZ from the configuration, or by carefully restricting the contents of the policy zone, for an affected configuration the most practical and safest course of action is to upgrade to a version of BIND without this vulnerability.
Upstream: Ramesh Damodaran (Infoblox) and Aliaksandr Shubnik (Infoblox)
Created attachment 1248550 [details]
Patch between bind-9.9.9-P6 and bind-9.9.9-P5
Public now via upstream advisory.
Created bind tracking bugs for this issue:
Affects: fedora-all [bug 1420607]
Created bind99 tracking bugs for this issue:
Affects: fedora-all [bug 1420608]
This issue has been addressed in the following products:
Red Hat Enterprise Linux 7
Via RHSA-2017:0276 https://rhn.redhat.com/errata/RHSA-2017-0276.html