First published: Wed Jan 16 2019(Updated: )
Change #4777 (introduced in October 2017) introduced an unforeseen issue in releases which were issued after that date, affecting which clients are permitted to make recursive queries to a BIND nameserver. The intended (and documented) behavior is that if an operator has not specified a value for the "allow-recursion" setting, it SHOULD default to one of the following: none, if "recursion no;" is set in named.conf; a value inherited from the "allow-query-cache" or "allow-query" settings IF "recursion yes;" (the default for that setting) AND match lists are explicitly set for "allow-query-cache" or "allow-query" (see the BIND9 Administrative Reference Manual section 6.2 for more details); or the intended default of "allow-recursion {localhost; localnets;};" if "recursion yes;" is in effect and no values are explicitly set for "allow-query-cache" or "allow-query". However, because of the regression introduced by change #4777, it is possible when "recursion yes;" is in effect and no match list values are provided for "allow-query-cache" or "allow-query" for the setting of "allow-recursion" to inherit a setting of all hosts from the "allow-query" setting default, improperly permitting recursion to all clients. Affects BIND 9.9.12, 9.10.7, 9.11.3, 9.12.0->9.12.1-P2, the development release 9.13.0, and also releases 9.9.12-S1, 9.10.7-S1, 9.11.3-S1, and 9.11.3-S2 from BIND 9 Supported Preview Edition.
Credit: security-officer@isc.org security-officer@isc.org
Affected Software | Affected Version | How to fix |
---|---|---|
ISC BIND | =9.9.12 | |
ISC BIND | =9.9.12-s1 | |
ISC BIND | =9.10.7 | |
ISC BIND | =9.10.7-s1 | |
ISC BIND | =9.11.3 | |
ISC BIND | =9.11.3-s1 | |
ISC BIND | =9.11.3-s2 | |
ISC BIND | =9.12.0 | |
ISC BIND | =9.12.0-a1 | |
ISC BIND | =9.12.0-b1 | |
ISC BIND | =9.12.0-b2 | |
ISC BIND | =9.12.0-rc1 | |
ISC BIND | =9.12.0-rc3 | |
ISC BIND | =9.12.1 | |
ISC BIND | =9.12.1-p1 | |
ISC BIND | =9.12.1-p2 | |
ISC BIND | =9.13.0 | |
Canonical Ubuntu Linux | =18.04 | |
debian/bind9 | 1:9.16.50-1~deb11u2 1:9.16.50-1~deb11u1 1:9.18.28-1~deb12u2 1:9.20.2-1 |
Future maintenance releases of BIND will correct the regression which introduced this issue but ISC does not believe that replacement security releases of BIND are required, given that several easy, safe, and completely effective configuration workarounds are available for any operators with affected configurations. However, an advance version of the patch diff which will be applied to future versions is available upon request to security-officer@isc.org and a correction for the behavior in question will debut in the release candidates for BIND 9.9.13, BIND 9.10.8, BIND 9.11.4, and BIND 9.12.2.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.