CVE-2014-3859: BIND named can crash due to a defect in EDNS printing processing
A specially crafted query sent to a BIND nameserver can cause it to crash with a REQUIRE assertion error.
Document version: 2.0
Posting date: 11 June 2014
Program impacted: BIND 9
Versions affected: 9.10.0, 9.10.0-P1
A query specially crafted to exploit a defect in EDNS option processing can cause named to terminate with an assertion failure.
Both authoritative and recursive servers are vulnerable to this defect. Exploitation of this condition can cause a denial of service in nameservers running affected versions of BIND 9.10. Access Control Lists do not provide protection.
The bug which causes this condition is in
libdns; consequently, in addition to the named server process, other applications (for example:
delv) built using the
libdns library from the affected source distributions can also be forced to crash with assertion failures triggered in the same fashion.
CVSS Score: 7.8
CVSS Equation: (AV:N/AC:L/Au:N/C:N/I:N/A:C)
For more information on the Common Vulnerability Scoring System and to obtain your specific environmental score please visit: http://nvd.nist.gov/cvss.cfm?calculator&adv&version=2&vector=(AV:N/AC:L/Au:N/C:N/I:N/A:C).
Workarounds: No known workarounds at this time.
Active exploits: There are no known active exploits.
Upgrade to the patched release most closely related to your current version of BIND. Open source versions can all be downloaded from https://www.isc.org/downloads.
- BIND 9 version 9.10.0-P2
Acknowledgements: ISC would like to thank Codenomicon for detecting this issue.
Document Revision History:
1.0 Phase One, Advance Notification, 04 June 2014
2.0 Phase Four, Public Disclosure, 11 June 2014
If you'd like more information on ISC Subscription Support and Advance Security Notifications, please visit https://www.isc.org/support/.
See our BIND 9 Security Vulnerability Matrix for a complete listing of security vulnerabilities and versions affected.
Do you still have questions? Questions regarding this advisory should go to email@example.com. To report a new issue, please encrypt your message using firstname.lastname@example.org's PGP key which can be found here: https://www.isc.org/downloads/software-support-policy/openpgp-key/. If you are unable to use encrypted email, you may also report new issues at: https://www.isc.org/community/report-bug/.
Note: ISC patches only currently supported versions. When possible, we indicate EOL versions affected. (For current information on which versions are actively supported, please see https://www.isc.org/downloads/.)
ISC Security Vulnerability Disclosure Policy: Details of our current security advisory policy and practice can be found in the ISC Software Defect and Security Vulnerability Disclosure Policy.
This Knowledgebase article is the complete and official security advisory document.
Legal Disclaimer: Internet Systems Consortium (ISC) is providing this notice on an "AS IS" basis. No warranty or guarantee of any kind is expressed in this notice and none should be implied. ISC expressly excludes and disclaims any warranties regarding this notice or materials referred to in this notice, including, without limitation, any implied warranty of merchantability, fitness for a particular purpose, absence of hidden defects, or of non-infringement. Your use or reliance on this notice or materials referred to in this notice is at your own risk. ISC may change this notice at any time. A stand-alone copy or paraphrase of the text of this document that omits the document URL is an uncontrolled copy. Uncontrolled copies may lack important information, be out of date, or contain factual errors.