First published: Thu Jun 07 2018(Updated: )
Ralph Dolmans and Karst Koymans discovered that Unbound did not properly handle certain NSEC records. An attacker could use this to to prove the non-existence (NXDOMAIN answer) of an existing wildcard record, or trick Unbound into accepting a NODATA proof.
Affected Software | Affected Version | How to fix |
---|---|---|
All of | ||
ubuntu/libunbound2 | <1.6.7-1ubuntu2.1 | 1.6.7-1ubuntu2.1 |
Ubuntu Ubuntu | =18.04 | |
All of | ||
ubuntu/unbound | <1.6.7-1ubuntu2.1 | 1.6.7-1ubuntu2.1 |
Ubuntu Ubuntu | =18.04 | |
All of | ||
ubuntu/libunbound2 | <1.6.5-1ubuntu0.2 | 1.6.5-1ubuntu0.2 |
Ubuntu Ubuntu | =17.10 | |
All of | ||
ubuntu/unbound | <1.6.5-1ubuntu0.2 | 1.6.5-1ubuntu0.2 |
Ubuntu Ubuntu | =17.10 | |
All of | ||
ubuntu/libunbound2 | <1.5.8-1ubuntu1.1 | 1.5.8-1ubuntu1.1 |
Ubuntu Ubuntu | =16.04 | |
All of | ||
ubuntu/unbound | <1.5.8-1ubuntu1.1 | 1.5.8-1ubuntu1.1 |
Ubuntu Ubuntu | =16.04 | |
All of | ||
ubuntu/libunbound2 | <1.4.22-1ubuntu4.14.04.3 | 1.4.22-1ubuntu4.14.04.3 |
Ubuntu Ubuntu | =14.04 | |
All of | ||
ubuntu/unbound | <1.4.22-1ubuntu4.14.04.3 | 1.4.22-1ubuntu4.14.04.3 |
Ubuntu Ubuntu | =14.04 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this Unbound vulnerability is USN-3673-1.
The severity of USN-3673-1 is not specified in the information provided.
The vulnerability affects Unbound by causing it to not properly handle certain NSEC records.
The impact of this vulnerability is that an attacker could use it to prove the non-existence (NXDOMAIN answer) of an existing wildcard record or trick Unbound into accepting a NODATA proof.
To fix the Unbound vulnerability, update the libunbound2 and unbound packages to the specified versions.