Vulnerability Note VU#714121

Incorrect NXDOMAIN responses from AAAA queries could cause denial-of-service conditions

Original Release date: 26 Mar 2003 | Last revised: 23 May 2003

Overview

Some DNS servers respond with an inappropriate error message if queried for nonexistent AAAA records, which can lead to possible denial of service.

Description

Some DNS servers respond with a "Name Error" response code (NXDOMAIN, RCODE 3) instead of "No Error" (RCODE 0) when queried for a nonexistent AAAA record. (AAAA records are used to provide name-to-address resolution for IPv6 addresses, as described in RFC1886.)

When an NXDOMAIN response code is received, the querying resolver will usually stop attempting to resolve that name. Resolvers that support negative caching (RFC2308) and receive an NXDOMAIN response will not query for A records for the same resource until the negatively cached error response has expired.

Sites operating DNS servers that respond to queries for nonexistent AAAA records with NXDOMAIN response codes may be susceptible to attackers using other sites' caching nameservers to block those other sites' users from resolving records in domains served by the broken DNS servers. Similar attacks may be possible against caching resolvers if an attacker were able to induce the resolver to look up a nonexistent AAAA record from a server acting in this manner.

Note: The same issue occurs with A6 records. However, A6 records (RFC2874) have been deemed "Experimental" by the IETF, with preference being given to AAAA records (RFC3363, RFC3364).

This is not a new issue. The NXDOMAIN in response to a AAAA query issue was noted in the (now expired) Internet Draft
draft-itojun-jinmei-ipv6-issues-00.txt:

    There are broken DNS servers that return NXDOMAIN against AAAA queries, when it should return NOERROR with empty return records.  When deploying IPv6/v4 dual stack node, it becomes problem because dual stack nodes would query AAAA first, see NXDOMAIN error, and won't try to query A records.  These broken DNS servers need to be corrected.
However, we have not seen this issue documented elsewhere as a potential denial-of-service attack vector against sites with their DNS servers broken in this manner.

Impact

An attacker could create a localized denial-of-service condition by exploting this vulnerability.

Solution

Apply a patch from your vendor.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
Cisco Systems Inc.Affected21 Mar 200323 May 2003
F5 NetworksNot Affected21 Mar 200323 May 2003
djbdnsUnknown21 Mar 200321 Mar 2003
ISCUnknown21 Mar 200321 Mar 2003
Microsoft CorporationUnknown21 Mar 200321 Mar 2003
Openwall GNU/*/LinuxUnknown21 Mar 200321 Mar 2003
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A

References

Credit

This document was written by Allen D Householder.

Other Information

  • CVE IDs: Unknown
  • Date Public: 24 Feb 2003
  • Date First Published: 26 Mar 2003
  • Date Last Updated: 23 May 2003
  • Severity Metric: 9.79
  • Document Revision: 10

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.