Bug 1461302 (CVE-2017-3140) - CVE-2017-3140 bind: Error processing RPZ rules leads to endless loop while handling query
Summary: CVE-2017-3140 bind: Error processing RPZ rules leads to endless loop while ha...
Alias: CVE-2017-3140
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1461639 1461641
Blocks: 1461305
TreeView+ depends on / blocked
Reported: 2017-06-14 07:27 UTC by Adam Mariš
Modified: 2021-02-17 02:02 UTC (History)
11 users (show)

Fixed In Version: bind 9.9.10-P1, bind 9.10.5-P1, bind 9.11.1-P1
Doc Type: If docs needed, set a value
Doc Text:
A denial of service flaw was found in the way BIND handled processing of NSDNAME and NSIP rules. A remote attacker could use this flaw to make named enter an infinite loop by sending a specially crafted query, thus resulting in denial-of-service.
Clone Of:
Last Closed: 2017-06-15 04:07:10 UTC

Attachments (Terms of Use)

Description Adam Mariš 2017-06-14 07:27:26 UTC
If named is configured to use Response Policy Zones (RPZ) an error processing some rule types can lead to a condition where BIND will endlessly loop while handling a query.

A server is potentially vulnerable to degradation of service if
    1. the server is configured to use RPZ,
    2. the server uses NSDNAME or NSIP policy rules, and
    3. an attacker can cause the server to process a specific query

Successful exploitation of this condition will cause named to enter a state where it continues to loop while processing the query without ever reaching an end state. While in this state, named repeatedly queries the same sets of authoritative nameservers and this behavior will usually persist indefinitely beyond the normal client query processing timeout. By triggering this condition multiple times, an attacker could cause a deliberate and substantial degradation in service.

Versions affected: 9.9.10, 9.10.5, 9.11.0->9.11.1, 9.9.10-S1, 9.10.5-S1


Only the NSDNAME and NSIP RPZ rule types can cause this condition to occur. You can work around this vulnerability if you are able to express your desired policy while avoiding NSDNAME or NSIP rules, otherwise it is advised that you upgrade to a version which corrects the defect.



Upstream patch:


Comment 1 Adam Mariš 2017-06-14 07:27:32 UTC

Name: Internet Systems Consortium
Upstream: Oli Schacher (Switch)

Comment 3 Dhiru Kholia 2017-06-15 03:35:22 UTC

This issue did not affect the versions of BIND as shipped with Red Hat Enterprise Linux 5, 6 and 7.

Comment 4 Dhiru Kholia 2017-06-15 03:44:13 UTC
Created bind99 tracking bugs for this issue:

Affects: fedora-all [bug 1461639]

Comment 6 Dhiru Kholia 2017-06-15 03:57:03 UTC
Created bind tracking bugs for this issue:

Affects: fedora-all [bug 1461641]

Note You need to log in before you can comment on or make changes to this bug.