BIND: allow-query processed incorrectly

Summary:

Using "allow-query" in the "options" or "view" statements to restrict access to authoritative zones has no effect.

CVE:

CVE-2010-3615

CERT:

VU#510208

Posting date:

01 Dec 2010

Program Impacted:

BIND

Versions affected:

9.7.2-P2

Severity:

High

Exploitable:

remotely

Description:

When named is running as an authoritative server for a zone and receives a query for that zone data, it first checks for allow-query acls in the zone statement, then in that view, then in global options. If none of these exist, it defaults to allowing any query (allow-query {"any"};).
With this bug, if the allow-query is not set in the zone statement, it failed to check in view or global options and fell back to the default of allowing any query. This means that queries that the zone owner did not wish to allow were incorrectly allowed.
This bug doesn't affect allow-recursion or allow-query-cache acls, since they are not relevant to a zone for which the server is authoritative.

CVSS: 7.8 - (AV:N/AC:L/Au:N/C:C/I:N/A:N) For more on CVSS scores and to calculate your environment's specific risk, please visit: CVSS Calculator: http://nvd.nist.gov/cvss.cfm?version=2&vector=(AV:N/AC:L/Au:N/C:C/I:N/A:N)

Impact and Risk Assessment:
The configured acl is not correctly applied, allowing queries that the owner did not wish to allow.

Workarounds:

Put the allow-query acl in each zone statement.

Active exploits:

None known at this time.

Solution:

Upgrade to 9.7.2-P3.
9.6ESV-R2 does not have this flaw. We are not patching EOL versions.

Revision History:
24Nov - Corrected/Updated Versions affected, CVSS Score and Solution

For more information please contact bind9-bugs@isc.org