First published: Tue Jan 23 2018(Updated: )
A flaw was found in the way unbound before 1.6.8 validated wildcard-synthesized NSEC records. An improperly validated wildcard NSEC record could be used to prove the non-existence (NXDOMAIN answer) of an existing wildcard record, or trick unbound into accepting a NODATA proof.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Nlnetlabs Unbound | <1.6.8 | |
Debian Debian Linux | =7.0 | |
Debian Debian Linux | =8.0 | |
Canonical Ubuntu Linux | =14.04 | |
Canonical Ubuntu Linux | =16.04 | |
Canonical Ubuntu Linux | =17.10 | |
Canonical Ubuntu Linux | =18.04 | |
debian/unbound | 1.13.1-1+deb11u2 1.13.1-1+deb11u3 1.17.1-2+deb12u2 1.21.1-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2017-15105.
The severity of CVE-2017-15105 is medium, with a severity value of 5.3.
The unbound software before versions 1.6.8 and 1.9.0-2+deb10u2 to 1.18.0-2 are affected by CVE-2017-15105.
To fix CVE-2017-15105, you should update unbound to version 1.6.8 or newer.
You can find more information about CVE-2017-15105 at the following references: [SecurityFocus](http://www.securityfocus.com/bid/102817), [Debian LTS Announce - January 2018](https://lists.debian.org/debian-lts-announce/2018/01/msg00039.html), [Debian LTS Announce - February 2019](https://lists.debian.org/debian-lts-announce/2019/02/msg00022.html).