VYPR

Bind

by Isc

Source repositories

CVEs (228)

  • CVE-2023-5679HigFeb 13, 2024
    risk 0.49cvss 7.5epss 0.01

    A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure during recursive resolution, when both of these features are enabled. This issue affects BIND 9 versions 9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19,…

  • CVE-2023-5517HigFeb 13, 2024
    risk 0.49cvss 7.5epss 0.01

    A flaw in query-handling code can cause `named` to exit prematurely with an assertion failure when: - `nxdomain-redirect ;` is configured, and - the resolver receives a PTR query for an RFC 1918 address that would normally result in an authoritative NXDOMAIN…

  • CVE-2023-4408HigFeb 13, 2024
    risk 0.49cvss 7.5epss 0.01

    The DNS message parsing code in `named` includes a section whose computational complexity is overly high. It does not cause problems for typical DNS traffic, but crafted queries and responses may cause excessive CPU load on the affected `named` instance by exploiting this flaw.…

  • CVE-2023-4236HigSep 20, 2023
    risk 0.49cvss 7.5epss 0.02

    A flaw in the networking code handling DNS-over-TLS queries may cause `named` to terminate unexpectedly due to an assertion failure. This happens when internal data structures are incorrectly reused under significant DNS-over-TLS query load. This issue affects BIND 9 versions…

  • CVE-2023-3341HigSep 20, 2023
    risk 0.49cvss 7.5epss 0.03

    The code that processes control channel messages sent to `named` calls certain functions recursively during packet parsing. Recursion depth is only limited by the maximum accepted packet size; depending on the environment, this may cause the packet-parsing code to run out of…

  • CVE-2023-2911HigJun 21, 2023
    risk 0.49cvss 7.5epss 0.02

    If the `recursive-clients` quota is reached on a BIND 9 resolver configured with both `stale-answer-enable yes;` and `stale-answer-client-timeout 0;`, a sequence of serve-stale-related lookups could cause `named` to loop and terminate unexpectedly due to a stack overflow. This…

  • CVE-2023-2829HigJun 21, 2023
    risk 0.49cvss 7.5epss 0.01

    A `named` instance configured to run as a DNSSEC-validating recursive resolver with the Aggressive Use of DNSSEC-Validated Cache (RFC 8198) option (`synth-from-dnssec`) enabled can be remotely terminated using a zone with a malformed NSEC record. This issue affects BIND 9…

  • CVE-2023-2828HigJun 21, 2023
    risk 0.49cvss 7.5epss 0.04

    Every `named` instance configured to run as a recursive resolver maintains a cache database holding the responses to the queries it has recently sent to authoritative servers. The size limit for that cache database can be configured using the `max-cache-size` statement in the…

  • CVE-2022-3080HigSep 21, 2022
    risk 0.49cvss 7.5epss 0.03

    By sending specific queries to the resolver, an attacker can cause named to crash.

  • CVE-2022-38178HigSep 21, 2022
    risk 0.49cvss 7.5epss 0.04

    By spoofing the target resolver with responses that have a malformed EdDSA signature, an attacker can trigger a small memory leak. It is possible to gradually erode available memory to the point where named crashes for lack of resources.

  • CVE-2022-38177HigSep 21, 2022
    risk 0.49cvss 7.5epss 0.05

    By spoofing the target resolver with responses that have a malformed ECDSA signature, an attacker can trigger a small memory leak. It is possible to gradually erode available memory to the point where named crashes for lack of resources.

  • CVE-2022-2906HigSep 21, 2022
    risk 0.49cvss 7.5epss 0.03

    An attacker can leverage this flaw to gradually erode available memory to the point where named crashes for lack of resources. Upon restart the attacker would have to begin again, but nevertheless there is the potential to deny service.

  • CVE-2022-1183HigMay 19, 2022
    risk 0.49cvss 7.5epss 0.06

    On vulnerable configurations, the named daemon may, in some circumstances, terminate with an assertion failure. Vulnerable configurations are those that include a reference to http within the listen-on statements in their named.conf. TLS is used by both DNS over TLS (DoT) and…

  • CVE-2022-0635HigMar 23, 2022
    risk 0.49cvss 7.5epss 0.01

    Versions affected: BIND 9.18.0 When a vulnerable version of named receives a series of specific queries, the named process will eventually terminate due to a failed assertion check.

  • CVE-2022-0667HigMar 22, 2022
    risk 0.49cvss 7.5epss 0.01

    When the vulnerability is triggered the BIND process will exit. BIND 9.18.0

  • CVE-2021-25218HigAug 18, 2021
    risk 0.49cvss 7.5epss 0.04

    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-2020-8623HigAug 21, 2020
    risk 0.49cvss 7.5epss 0.07

    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…

  • CVE-2020-8621HigAug 21, 2020
    risk 0.49cvss 7.5epss 0.03

    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…

  • CVE-2020-8620HigAug 21, 2020
    risk 0.49cvss 7.5epss 0.04

    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-2019-6477HigNov 26, 2019
    risk 0.49cvss 7.5epss 0.04

    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…

Page 4 of 12