First published: Fri Aug 21 2020(Updated: )
In BIND 9.14.0 -> 9.16.5, 9.17.0 -> 9.17.3, If a server is configured with both QNAME minimization and 'forward first' then an attacker who can send queries to it may be able to trigger the condition that will cause the server to crash. Servers that 'forward only' are not affected.
Credit: security-officer@isc.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/bind9 | 1:9.16.50-1~deb11u2 1:9.16.50-1~deb11u3 1:9.18.28-1~deb12u2 1:9.18.33-1~deb12u2 1:9.20.4-4 1:9.20.5-1 | |
ISC BIND 9 | >=9.14.0<=9.16.5 | |
ISC BIND 9 | >=9.17.0<=9.17.3 | |
SUSE Linux | =15.1 | |
SUSE Linux | =15.2 | |
Ubuntu | =16.04 | |
Ubuntu | =18.04 | |
Ubuntu | =20.04 | |
Synology DNS Server | <2.2.2-5027 | |
NetApp SteelStore Cloud Integrated Storage |
Upgrade to the patched release most closely related to your current version of BIND: BIND 9.16.6 BIND 9.17.4
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2020-8621 is high with a severity value of 7.5.
BIND versions 9.14.0 to 9.16.5 and 9.17.0 to 9.17.3 are affected by CVE-2020-8621.
An attacker can exploit CVE-2020-8621 by sending queries to a BIND server configured with both QNAME minimization and 'forward first', causing the server to crash.
No, servers configured with 'forward only' are not affected by CVE-2020-8621.
To fix CVE-2020-8621, update your BIND server to a version that includes the fix for the vulnerability.