Red Hat Bugzilla – Full Text Bug Listing
|Summary:||CVE-2012-5166 bind: Specially crafted DNS data can cause a lockup in named|
|Product:||[Other] Security Response||Reporter:||Huzaifa S. Sidhpurwala <huzaifas>|
|Component:||vulnerability||Assignee:||Red Hat Product Security <security-response-team>|
|Status:||CLOSED ERRATA||QA Contact:|
|Version:||unspecified||CC:||atkac, jlieskov, johan.bergstrom, raina, rpacheco, rwahyudi, security-response-team, zzhou|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2012-10-12 16:38:27 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:||859916, 864748, 864749, 864750, 864751, 864753, 864754, 864756|
Description Huzaifa S. Sidhpurwala 2012-10-08 23:17:11 EDT
A flaw in ISC BIND was reported where, if specific combinations of RDATA are loaded into a nameserver, either via cache or an authoritative zone, a subsequent query for a related record will cause named to lock up. This vulnerability can be exploited remotely against recursive servers by inducing them to query for records provided by an authoritative server. It affects authoritative servers if one of the combinations of resource records is loaded from file, provided via zone transfer, or submitted to a zone via dynamic update. Once bind becomes locked-up due to the above issue, it will not respond to queries or control commands. Normal functionality can only be restored by restarting named. Workaround: Setting the option 'minimal-responses' to 'yes' will prevent the lockup.
Comment 4 Vincent Danen 2012-10-09 18:43:25 EDT
External References: https://kb.isc.org/article/AA-00801
Comment 5 Vincent Danen 2012-10-09 18:44:52 EDT
Created attachment 624300 [details] diff of bind-9.6-ESV-R7-P3 to P4 The relevant bits of the diff between versions with this changelog entry: 3383. [security] A certain combination of records in the RBT could cause named to hang while populating the additional section of a response. [RT #31090]
Comment 7 Huzaifa S. Sidhpurwala 2012-10-09 23:06:45 EDT
This issue affects the version of bind as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of bind97 as shipped with Red Hat Enterprise Linux 5. This issue affects the version of bind as shipped with Fedora 16 and Fedora 17
Comment 10 Huzaifa S. Sidhpurwala 2012-10-09 23:11:06 EDT
Created bind tracking bugs for this issue Affects: fedora-all [bug 864756]
Comment 14 errata-xmlrpc 2012-10-12 15:43:50 EDT
This issue has been addressed in following products: Red Hat Enterprise Linux 4 Extended Lifecycle Support Via RHSA-2012:1365 https://rhn.redhat.com/errata/RHSA-2012-1365.html
Comment 15 errata-xmlrpc 2012-10-12 15:44:36 EDT
This issue has been addressed in following products: Red Hat Enterprise Linux 5 Via RHSA-2012:1364 https://rhn.redhat.com/errata/RHSA-2012-1364.html
Comment 16 errata-xmlrpc 2012-10-12 15:44:45 EDT
This issue has been addressed in following products: Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 6 Via RHSA-2012:1363 https://rhn.redhat.com/errata/RHSA-2012-1363.html
Comment 17 Fedora Update System 2012-10-19 19:59:32 EDT
dhcp-4.2.4-16.P2.fc17, bind-dyndb-ldap-1.1.0-0.15.rc1.fc17, bind-9.9.2-2.fc17, dnsperf-184.108.40.206-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
Comment 18 Fedora Update System 2012-10-21 02:15:19 EDT
dhcp-4.2.4-18.P2.fc18, bind-dyndb-ldap-2.0-0.3.20121009git6a86b1.fc18, bind-9.9.2-2.fc18, dnsperf-220.127.116.11-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Comment 19 Fedora Update System 2012-10-22 21:52:28 EDT
dhcp-4.2.4-4.P2.fc16, bind-dyndb-ldap-1.1.0-0.15.rc1.fc16, bind-9.8.4-2.fc16, dnsperf-18.104.22.168-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.