Vulnerability Note VU#209659
Unbound multiple denial-of-service vulnerabilities
A specially crafted DNS query containing signed duplicate resource records or a malformed NSEC3 signed resource record may cause Unbound to crash.
NLnetLabs advisory states:
== Description 1: crash on signed duplicate Resource Records
There are authoritative servers that erroneously send duplicated redirection Resource Records. Unbound has had a workaround that deals with this problem since version 1.0.1 whereby it ignores the duplicate answers. At the time, likely, no DNSSEC signed versions of such zones existed and only recently such misbehaving authority servers also started serving signed duplicate RRs causing improper memory allocation in a portion of the workaround code.
Referencing this improper allocated data causes a crash which can look like 'uninitialised lock', segmentation faults or free() errors as it tries to free memory that was never allocated.
== Description 2: crash on missing NSEC3 Resource Records.
If an authority server sends a reply for an NSEC3-signed zone, and Unbound is configured to validate that zone, then a malformed response can trigger an assertion failure: when an authority server sends a response that contains RR types that trigger special processing and where part of the non-existence proof is missing then an assertion failure is triggered in unbound. This response case was observed in the wild on authority servers that host zones at different points in the hierarchy at the same time.
The code crashes at assertion failure validator/val_nsec3.c:1214: nsec3_do_prove_nodata: assertion ce.nc_rrset failed Or, if assertions are not compiled it, it crashes soon after as it attempts to access an expected NSEC3 RR.
Additional details can be found in the full NLnetLabs Unbound advisory.
A remote, unauthenticated attacker could cause the Unbound daemon to crash creating a denial-of-service condition.
Vendor Information (Learn More)
If you are a vendor and your product is affected, let
|Vendor||Status||Date Notified||Date Updated|
|NLnet Labs||Affected||14 Dec 2011||19 Dec 2011|
This vulnerability was found by Christopher Olah and reported by NLnetLabs.
This document was written by Michael Orlando.
19 Dec 2011
Date First Published:
19 Dec 2011
Date Last Updated:
19 Dec 2011
If you have feedback, comments, or additional information about this vulnerability, please send us email.