A flaw was found in BIND where the "allow-query" in the "options" or "view" statements to restrict access to authoritative zones had no effect [1]. The advisory states: "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." The upstream advisory [2] notes that this affects BIND version 9.7.2-P2 and is corrected in 9.7.2-P3. [1] http://www.isc.org/announcement/guidance-regarding-dec-1st-2010-security-advisories [2] http://www.isc.org/software/bind/advisories/cve-2010-3615
Created bind tracking bugs for this issue Affects: fedora-14 [bug 658987]
Statement: Not vulnerable. This issue did not affect the versions of bind as shipped with Red Hat Enterprise Linux 4, 5, or 6.
I think the type should be NOTABUG.
The issue was addressed in Fedora 14, which is one of the products using Red Hat Bugzilla for tracking: http://lists.fedoraproject.org/pipermail/package-announce/2010-December/051963.html We tend to use CLOSED:ERRATA when at least one product was affected and fixed.