Bug 970905 (CVE-2013-3919)

Summary: CVE-2013-3919 bind: Querying a recursive resolver for a malformed zone causes named to crash
Product: [Other] Security Response Reporter: Huzaifa S. Sidhpurwala <huzaifas>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: jlieskov, thozza, vonsch
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: bind 9.9.3-P1, bind 9.8.5-P1, bind 9.6-ESV-R9-P1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-05 09:39:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 970911    
Attachments:
Description Flags
diff of bind-9.6-ESV-R9-P1 and bind-9.6-ESV-R9 none

Description Huzaifa S. Sidhpurwala 2013-06-05 07:57:33 UTC 
A flaw in ISC BIND was reported [1] where a recursive nameserver could be caused to crash if it recieved a query for a record in a specially malformed zone. A remote attacker could use this flaw to remotely exploit (Denial of Service) a recursive nameserver, by sending a query for a malformed zone, which could cause BIND to exit with a fatal "RUNTIME_CHECK" error in resolver.c

[1] https://kb.isc.org/article/AA-00967

Affected versions: BIND 9.6-ESV-R9, 9.8.5, and 9.9.3 are affected

Note:
Versions 9.6.0 through 9.6-ESV-R8, 9.8.0 through 9.8.4-P2, and 9.9.0 through 9.9.2-P2 ARE NOT affected. Also other major branches of BIND (e.g. 9.7, 9.5, etc) are NOT vulnerable to this flaw.
Comment 1 Huzaifa S. Sidhpurwala 2013-06-05 08:00:27 UTC 
Created attachment 757073 [details]
diff of bind-9.6-ESV-R9-P1 and bind-9.6-ESV-R9
Comment 2 Huzaifa S. Sidhpurwala 2013-06-05 08:13:18 UTC 
Statement:

Not Vulnerable. This issue does not affect the version of bind as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of bind97 as shipped with Red Hat Enterprise Linux 5.
Comment 3 Huzaifa S. Sidhpurwala 2013-06-05 08:26:16 UTC 
Fedora 17 ships bind-9.9.2-7.P2.fc17 and Fedora 18 ships bind-9.9.2-10.P2.fc18, and therefore are not affected by this issue.

However the update candidates for bind are affected:

https://admin.fedoraproject.org/updates/dhcp-4.2.5-2.fc17,dnsperf-2.0.0.0-3.fc17,bind-dyndb-ldap-2.5-2.fc17,bind-9.9.3-2.fc17
https://admin.fedoraproject.org/updates/bind-dyndb-ldap-2.6-2.fc18,dnsperf-2.0.0.0-4.fc18,dhcp-4.2.5-12.fc18,bind-9.9.3-2.fc18
https://admin.fedoraproject.org/updates/FEDORA-2013-9984/bind-9.9.3-2.fc19

Please schedule an update to replace these builds with the fixed versions.