opensuse/bind&distro=openSUSE Tumbleweed

Vulnerabilities (109)

• CVE-2021-25218Aug 18, 2021
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  In BIND 9.16.19, 9.17.16. Also, version 9.16.19-S1 of BIND Supported Preview Edition When a vulnerable version of named receives a query under the circumstances described above, the named process will terminate due to a failed assertion check. The vulnerability affects only BIND

• CVE-2021-25216Apr 29, 2021
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  In BIND 9.5.0 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.11.3-S1 -> 9.11.29-S1 and 9.16.8-S1 -> 9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.1 of the BIND 9.17 development branch, BIND servers are vulnerable if they are running

• CVE-2021-25215Apr 29, 2021
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  In BIND 9.0.0 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and 9.16.8-S1 -> 9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11 of the BIND 9.17 development branch, when a vulnerable version of named receives a qu

• CVE-2021-25214Apr 29, 2021
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  In BIND 9.8.5 -> 9.8.8, 9.9.3 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and 9.16.8-S1 -> 9.16.13-S1 of BIND 9 Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11 of the BIND 9.17 development branch, when a vulnerable version of n

• CVE-2020-8625Feb 17, 2021
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  BIND servers are vulnerable if they are running an affected version and are configured to use GSS-TSIG features. In a configuration which uses BIND's default settings the vulnerable code path is not exposed, but a server can be rendered vulnerable by explicitly setting valid valu

• CVE-2020-8624Aug 21, 2020
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  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 specific subset of the

• CVE-2020-8623Aug 21, 2020
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  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 vulnerable, the system must

• CVE-2020-8622Aug 21, 2020
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  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, could send a truncated

• CVE-2020-8621Aug 21, 2020
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  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 affecte

• CVE-2020-8620Aug 21, 2020
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  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 data on that connection can exploit this to trigger the assertion failure, causing the server to exit.

• CVE-2020-8619Jun 17, 2020
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  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 an empty non-terminal

• CVE-2020-8618Jun 17, 2020
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  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.

• CVE-2020-8617May 19, 2020
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  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 even on servers whos

• CVE-2020-8616May 19, 2020
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  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 in an attempt to proce

• CVE-2019-6477Nov 26, 2019
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  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 the server has been pr

• CVE-2019-6476Oct 17, 2019
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  A defect in code added to support QNAME minimization can cause named to exit with an assertion failure if a forwarder returns a referral rather than resolving the query. This affects BIND versions 9.14.0 up to 9.14.6, and 9.15.0 up to 9.15.4.

• CVE-2019-6471Oct 9, 2019
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  A race condition which may occur when discarding malformed packets can result in BIND exiting due to a REQUIRE assertion failure in dispatch.c. Versions affected: BIND 9.11.0 -> 9.11.7, 9.12.0 -> 9.12.4-P1, 9.14.0 -> 9.14.2. Also all releases of the BIND 9.13 development branch a

• CVE-2019-6465Oct 9, 2019
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  Controls for zone transfers may not be properly applied to Dynamically Loadable Zones (DLZs) if the zones are writable Versions affected: BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.5-P2, 9.12.0 -> 9.12.3-P2, and versions 9.9.3-S1 -> 9.11.5-S3 of BIND 9 Supported Preview Edition. Ver

• CVE-2018-5745Oct 9, 2019
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  "managed-keys" is a feature which allows a BIND resolver to automatically maintain the keys used by trust anchors which operators configure for use in DNSSEC validation. Due to an error in the managed-keys feature it is possible for a BIND server which uses managed-keys to exit d

• CVE-2018-5743Oct 9, 2019
  affected < 9.16.20-1.4fixed 9.16.20-1.4

  By design, BIND is intended to limit the number of TCP clients that can be connected at any given time. The number of allowed connections is a tunable parameter which, if unset, defaults to a conservative value for most servers. Unfortunately, the code which was intended to limit