Skip to content
OpenAdvisories
High openSUSE-SU-2020:1701-1 12 CVEs

Security update for bind

Published Oct 20, 2020 · Updated Feb 4, 2026

Summary

This update for bind fixes the following issues:

BIND was upgraded to version 9.16.6:

Note:

- bind is now more strict in regards to DNSSEC. If queries are not working,
check for DNSSEC issues. For instance, if bind is used in a namserver
forwarder chain, the forwarding DNS servers must support DNSSEC.

Fixing security issues:

- CVE-2020-8616: Further limit the number of queries that can be triggered from
a request. Root and TLD servers are no longer exempt
from max-recursion-queries. Fetches for missing name server. (bsc#1171740)
Address records are limited to 4 for any domain.
- CVE-2020-8617: Replaying a TSIG BADTIME response as a request could trigger an
assertion failure. (bsc#1171740)
- CVE-2019-6477: Fixed an issue where TCP-pipelined queries could bypass
the tcp-clients limit (bsc#1157051).
- CVE-2018-5741: Fixed the documentation (bsc#1109160).
- CVE-2020-8618: It was possible to trigger an INSIST when determining
whether a record would fit into a TCP message buffer (bsc#1172958).
- CVE-2020-8619: It was possible to trigger an INSIST in
lib/dns/rbtdb.c:new_reference() with a particular zone content
and query patterns (bsc#1172958).
- CVE-2020-8624: 'update-policy' rules of type 'subdomain' were
incorrectly treated as 'zonesub' rules, which allowed
keys used in 'subdomain' rules to update names outside
of the specified subdomains. The problem was fixed by
making sure 'subdomain' rules are again processed as
described in the ARM (bsc#1175443).
- CVE-2020-8623: When BIND 9 was compiled with native PKCS#11 support, it
was possible to trigger an assertion failure in code
determining the number of bits in the PKCS#11 RSA public
key with a specially crafted packet (bsc#1175443).
- CVE-2020-8621: named could crash in certain query resolution scenarios
where QNAME minimization and forwarding were both
enabled (bsc#1175443).
- CVE-2020-8620: It was possible to trigger an assertion failure by
sending a specially crafted large TCP DNS message (bsc#1175443).
- CVE-2020-8622: It was possible to trigger an assertion failure when
verifying the response to a TSIG-signed request (bsc#1175443).

Other issues fixed:

- Add engine support to OpenSSL EdDSA implementation.
- Add engine support to OpenSSL ECDSA implementation.
- Update PKCS#11 EdDSA implementation to PKCS#11 v3.0.
- Warn about AXFR streams with inconsistent message IDs.
- Make ISC rwlock implementation the default again.
- Fixed issues when using cookie-secrets for AES and SHA2 (bsc#1161168)
- Installed the default files in /var/lib/named and created
chroot environment on systems using transactional-updates (bsc#1100369, fate#325524)
- Fixed an issue where bind was not working in FIPS mode (bsc#906079).
- Fixed dependency issues (bsc#1118367 and bsc#1118368).
- GeoIP support is now discontinued, now GeoIP2 is used(bsc#1156205).
- Fixed an issue with FIPS (bsc#1128220).
- The liblwres library is discontinued upstream and is no longer included.
- Added service dependency on NTP to make sure the clock is accurate when bind is starts (bsc#1170667, bsc#1170713).
- Reject DS records at the zone apex when loading master files. Log but otherwise ignore attempts to add DS records at the zone apex via UPDATE.
- The default value of 'max-stale-ttl' has been changed from 1 week to 12 hours.
- Zone timers are now exported via statistics channel.
- The 'primary' and 'secondary' keywords, when used as parameters for 'check-names', were not processed correctly and were being ignored.
- 'rndc dnstap -roll <value>' did not limit the number of saved files to <value>.
- Add 'rndc dnssec -status' command.
- Addressed a couple of situations where named could crash.
- Changed /var/lib/named to owner root:named and perms rwxrwxr-t
so that named, being a/the only member of the 'named' group
has full r/w access yet cannot change directories owned by root
in the case of a compromized named.
[bsc#1173307, bind-chrootenv.conf]
- Added '/etc/bind.keys' to NAMED_CONF_INCLUDE_FILES in /etc/sysconfig/named to suppress warning message re missing file (bsc#1173983).
- Removed '-r /dev/urandom' from all invocations of rndc-confgen
(init/named system/lwresd.init system/named.init in vendor-files)
as this option is deprecated and causes rndc-confgen to fail.
(bsc#1173311, bsc#1176674, bsc#1170713)
- /usr/bin/genDDNSkey: Removing the use of the -r option in the call
of /usr/sbin/dnssec-keygen as BIND now uses the random number
functions provided by the crypto library (i.e., OpenSSL or a
PKCS#11 provider) as a source of randomness rather than /dev/random.
Therefore the -r command line option no longer has any effect on
dnssec-keygen. Leaving the option in genDDNSkey as to not break
compatibility. Patch provided by Stefan Eisenwiener.
[bsc#1171313]
- Put libns into a separate subpackage to avoid file conflicts
in the libisc subpackage due to different sonums (bsc#1176092).
- Require /sbin/start_daemon: both init scripts, the one used in
systemd context as well as legacy sysv, make use of start_daemon.

This update was imported from the SUSE:SLE-15:Update update project.

Fixed packages 3

ReleasePackageFixed in
openSUSE · Leap 15.1 bind 9.16.6-lp151.11.9.1
openSUSE · Leap 15.1 libuv 1.18.0-lp151.3.3.1
openSUSE · Leap 15.1 sysuser-tools 2.0-lp151.4.3.1

Vulnerabilities 12

  • High 8.6
    CVE-2020-8616 EPSS 11%

    BIND does not sufficiently limit the number of fetches performed when processing referrals

    A malicious actor who intentionally exploits this lack of effective limitation on the number of fetches performed when processing referrals can, through the use of specially crafted referrals, cause a recursing server to issue a very large number of fetches i…

  • High 7.5

    TCP-pipelined queries can bypass tcp-clients limit

    With pipelining enabled each incoming query on a TCP connection requires a similar resource allocation to a query received via UDP or via TCP without pipelining enabled. A client using a TCP-pipelined connection to a server could consume more resources than t…

  • High 7.5
    CVE-2020-8617 Public exploit EPSS 93%

    A logic error in code which checks TSIG validity can be used to trigger an assertion failure in tsig.c

    Using a specially-crafted message, an attacker may potentially cause a BIND server to reach an inconsistent state if the attacker knows (or successfully guesses) the name of a TSIG key used by the server. Since BIND, by default, configures a local session key…

  • High 7.5

    In BIND 9.15.6 -> 9.16.5, 9.17.0 -> 9.17.3, An attacker who can establish a TCP connection with the server and send dat…

  • High 7.5

    Attempting QNAME minimization after forwarding can lead to an assertion failure in resolver.c

    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 …

  • High 7.5

    A flaw in native PKCS#11 code can lead to a remotely triggerable assertion failure in pk11.c

    In BIND 9.10.0 -> 9.11.21, 9.12.0 -> 9.16.5, 9.17.0 -> 9.17.3, also affects 9.10.5-S1 -> 9.11.21-S1 of the BIND 9 Supported Preview Edition, An attacker that can reach a vulnerable system with a specially crafted query packet can trigger a crash. To be vulner…

  • Medium 6.5

    Update policies krb5-subdomain and ms-subdomain do not enforce controls promised in their documentation

    To provide fine-grained controls over the ability to use Dynamic DNS (DDNS) to update records in a zone, BIND 9 provides a feature called update-policy. Various rules can be configured to limit the types of updates that can be performed by a client, depending…

  • Medium 6.5

    A truncated TSIG response can lead to an assertion failure

    In BIND 9.0.0 -> 9.11.21, 9.12.0 -> 9.16.5, 9.17.0 -> 9.17.3, also affects 9.9.3-S1 -> 9.11.21-S1 of the BIND 9 Supported Preview Edition, An attacker on the network path for a TSIG-signed request, or operating the server receiving the TSIG-signed request, co…

  • Medium 5.9
    CVE-2017-3136 EPSS 11%

    An error handling synthesized records could cause an assertion failure when using DNS64 with "break-dnssec yes;"

    A query with a specific set of characteristics could cause a server using DNS64 to encounter an assertion failure and terminate. An attacker could deliberately construct a query, enabling denial-of-service against a server if it was configured to use the DNS6…

  • Medium 4.9

    A buffer boundary check assertion in rdataset.c can fail incorrectly during zone transfer

    An attacker who is permitted to send zone data to a server via zone transfer can exploit this to intentionally trigger the assertion failure with a specially constructed zone, denying service to clients.

  • Medium 4.9

    A buffer boundary check assertion in rdataset.c can fail incorrectly during zone transfer

    In ISC BIND9 versions BIND 9.11.14 -> 9.11.19, BIND 9.14.9 -> 9.14.12, BIND 9.16.0 -> 9.16.3, BIND Supported Preview Edition 9.11.14-S1 -> 9.11.19-S1: Unless a nameserver is providing authoritative service for one or more zones and at least one zone contains …

  • Medium 4.3

    update-policy rules of type "subdomain" are enforced incorrectly

    In BIND 9.9.12 -> 9.9.13, 9.10.7 -> 9.10.8, 9.11.3 -> 9.11.21, 9.12.1 -> 9.16.5, 9.17.0 -> 9.17.3, also affects 9.9.12-S1 -> 9.9.13-S1, 9.11.3-S1 -> 9.11.21-S1 of the BIND 9 Supported Preview Edition, An attacker who has been granted privileges to change a sp…

References

  • report
    https://bugzilla.suse.com/1100369
  • report
    https://bugzilla.suse.com/1109160
  • report
    https://bugzilla.suse.com/1118367
  • report
    https://bugzilla.suse.com/1118368
  • report
    https://bugzilla.suse.com/1128220
  • report
    https://bugzilla.suse.com/1156205
  • report
    https://bugzilla.suse.com/1157051
  • report
    https://bugzilla.suse.com/1161168
  • report
    https://bugzilla.suse.com/1170667
  • report
    https://bugzilla.suse.com/1170713
  • report
    https://bugzilla.suse.com/1171313
  • report
    https://bugzilla.suse.com/1171740
  • report
    https://bugzilla.suse.com/1172958
  • report
    https://bugzilla.suse.com/1173307
  • report
    https://bugzilla.suse.com/1173311
  • report
    https://bugzilla.suse.com/1173983
  • report
    https://bugzilla.suse.com/1175443
  • report
    https://bugzilla.suse.com/1176092
  • report
    https://bugzilla.suse.com/1176674
  • report
    https://bugzilla.suse.com/906079
  • web
    https://www.suse.com/security/cve/CVE-2017-3136
  • web
    https://www.suse.com/security/cve/CVE-2018-5741
  • web
    https://www.suse.com/security/cve/CVE-2019-6477
  • web
    https://www.suse.com/security/cve/CVE-2020-8616
  • web
    https://www.suse.com/security/cve/CVE-2020-8617
  • web
    https://www.suse.com/security/cve/CVE-2020-8618
  • web
    https://www.suse.com/security/cve/CVE-2020-8619
  • web
    https://www.suse.com/security/cve/CVE-2020-8620
  • web
    https://www.suse.com/security/cve/CVE-2020-8621
  • web
    https://www.suse.com/security/cve/CVE-2020-8622
  • web
    https://www.suse.com/security/cve/CVE-2020-8623
  • web
    https://www.suse.com/security/cve/CVE-2020-8624