CVE-2014-3214: A Defect in Prefetch Can Cause Recursive Servers to Crash

Michael McNally mcnally at
Thu May 8 20:04:19 UTC 2014

A defect in the prefetch feature can cause named to crash when
handling some queries.

CVE:                       CVE-2014-3214
Document Version:          2.0
Posting date:              8 May 2014
Program Impacted:          BIND
Versions affected:         9.10.0
Severity:                  High
Exploitable:               Remotely


   A defect in the pre-fetch feature (which is enabled by default)
   can cause BIND 9.10.0 to terminate with a "REQUIRE" assertion
   failure if it processes queries whose answers have particular
   attributes.  This can be triggered as the result of normal query


   Recursive nameservers are vulnerable to this defect.  Authoritative-only
   servers are not at risk.  On an affected nameserver, the assertion
   failure, if triggered, results in an immediate exit from named,
   denying service to clients attempting to query the recursive

CVSS Score:                7.8

CVSS Vector:               (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:


   The problematic code is bypassed and prefetching is disabled by
   setting the prefetch option to zero within the options block 
   in named.conf:

      prefetch 0;

Active exploits: 

   There are no known active exploits but the crash has been
   independently reported by multiple organizations.


   Upgrade to the patched release listed below.  BIND software can
   be downloaded from

   -  BIND 9 version 9.10.0-P1 


   ISC would like to thank each of the individuals who independently
   discovered and reported the problem.

Document Revision History:

   1.0 Phase One, Advance Notification 7 May 2014
   2.0 Phase Four, Public Disclosure: 8 May 2014

Related Documents:

   See our BIND Security Matrix ( )
   for a complete listing of Security Vulnerabilities and versions affected.

If you'd like more information on ISC product support please visit

Do you still have questions?  Questions regarding this advisory
should go to security-officer at  To report a new issue,
please encrypt your message using security-officer at's PGP
key which can be found here: 

If you are unable to use encrypted email, you may also report new
issues at:


   ISC patches only currently supported versions.
   When possible we indicate EOL versions affected.

   ISC Security Vulnerability Disclosure Policy:  Details of our
   current security advisory policy and practice can be found here:

   This Knowledge Base 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.

(c) 2001-2014 Internet Systems Consortium

More information about the bind-announce mailing list