VYPR

rpm package

almalinux/bind9.16-libs

pkg:rpm/almalinux/bind9.16-libs

Vulnerabilities (40)

  • CVE-2024-4076HigJul 23, 2024
    affected < 32:9.16.23-0.22.el8_10fixed 32:9.16.23-0.22.el8_10

    Client queries that trigger serving stale data and that also require lookups in local authoritative zone data may result in an assertion failure. This issue affects BIND 9 versions 9.16.13 through 9.16.50, 9.18.0 through 9.18.27, 9.19.0 through 9.19.24, 9.11.33-S1 through 9.11.37

  • CVE-2024-1975HigJul 23, 2024
    affected < 32:9.16.23-0.22.el8_10fixed 32:9.16.23-0.22.el8_10

    If a server hosts a zone containing a "KEY" Resource Record, or a resolver DNSSEC-validates a "KEY" Resource Record from a DNSSEC-signed domain in cache, a client can exhaust resolver CPU resources by sending a stream of SIG(0) signed requests. This issue affects BIND 9 versions

  • CVE-2024-1737HigJul 23, 2024
    affected < 32:9.16.23-0.22.el8_10fixed 32:9.16.23-0.22.el8_10

    Resolver caches and authoritative zone databases that hold significant numbers of RRs for the same hostname (of any RTYPE) can suffer from degraded performance as content is being added or updated, and also when handling client queries for this name. This issue affects BIND 9 ver

  • CVE-2023-50868HigFeb 14, 2024
    affected < 32:9.16.23-0.16.el8_9.2.alma.1fixed 32:9.16.23-0.16.el8_9.2.alma.1

    The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 51

  • CVE-2023-50387HigFeb 14, 2024
    affected < 32:9.16.23-0.16.el8_9.2.alma.1fixed 32:9.16.23-0.16.el8_9.2.alma.1

    Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with man

  • CVE-2023-6516HigFeb 13, 2024
    affected < 32:9.16.23-0.16.el8_9.2.alma.1fixed 32:9.16.23-0.16.el8_9.2.alma.1

    To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to clean up the database. It uses several methods, including some that are asynchronous: a small chunk of memory pointing to the cache element that can be cleaned up is first alloc

  • CVE-2023-5679HigFeb 13, 2024
    affected < 32:9.16.23-0.16.el8_9.2.alma.1fixed 32:9.16.23-0.16.el8_9.2.alma.1

    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, 9

  • CVE-2023-5517HigFeb 13, 2024
    affected < 32:9.16.23-0.16.el8_9.2.alma.1fixed 32:9.16.23-0.16.el8_9.2.alma.1

    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 response

  • CVE-2023-4408HigFeb 13, 2024
    affected < 32:9.16.23-0.16.el8_9.2.alma.1fixed 32:9.16.23-0.16.el8_9.2.alma.1

    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. T

  • CVE-2023-3341HigSep 20, 2023
    affected < 32:9.16.23-0.14.el8_8.2.alma.1fixed 32:9.16.23-0.14.el8_8.2.alma.1

    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 avai

  • CVE-2023-2828HigJun 21, 2023
    affected < 32:9.16.23-0.14.el8_8.1.almafixed 32:9.16.23-0.14.el8_8.1.alma

    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 con

  • CVE-2022-3924HigJan 26, 2023
    affected < 32:9.16.23-0.14.el8fixed 32:9.16.23-0.14.el8

    This issue can affect BIND 9 resolvers with `stale-answer-enable yes;` that also make use of the option `stale-answer-client-timeout`, configured with a value greater than zero. If the resolver receives many queries that require recursion, there will be a corresponding increase

  • CVE-2022-3736HigJan 26, 2023
    affected < 32:9.16.23-0.14.el8fixed 32:9.16.23-0.14.el8

    BIND 9 resolver can crash when stale cache and stale answers are enabled, option `stale-answer-client-timeout` is set to a positive integer, and the resolver receives an RRSIG query. This issue affects BIND 9 versions 9.16.12 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 throug

  • CVE-2022-3094HigJan 26, 2023
    affected < 32:9.16.23-0.14.el8fixed 32:9.16.23-0.14.el8

    Sending a flood of dynamic DNS updates may cause `named` to allocate large amounts of memory. This, in turn, may cause `named` to exit due to a lack of free memory. We are not aware of any cases where this has been exploited. Memory is allocated prior to the checking of access p

  • CVE-2022-3080HigSep 21, 2022
    affected < 32:9.16.23-0.7.el8_6.1fixed 32:9.16.23-0.7.el8_6.1

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

  • CVE-2022-38178HigSep 21, 2022
    affected < 32:9.16.23-0.7.el8_6.1fixed 32:9.16.23-0.7.el8_6.1

    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
    affected < 32:9.16.23-0.7.el8_6.1fixed 32:9.16.23-0.7.el8_6.1

    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-2795MedSep 21, 2022
    affected < 32:9.16.23-0.14.el8fixed 32:9.16.23-0.14.el8

    By flooding the target resolver with queries exploiting this flaw an attacker can significantly impair the resolver's performance, effectively denying legitimate clients access to the DNS resolution service.

  • CVE-2021-25220MedMar 23, 2022
    affected < 32:9.16.23-0.9.el8.1fixed 32:9.16.23-0.9.el8.1

    BIND 9.11.0 -> 9.11.36 9.12.0 -> 9.16.26 9.17.0 -> 9.18.0 BIND Supported Preview Editions: 9.11.4-S1 -> 9.11.36-S1 9.16.8-S1 -> 9.16.26-S1 Versions of BIND 9 earlier than those shown - back to 9.1.0, including Supported Preview Editions - are also believed to be affected but have

  • CVE-2022-0396MedMar 23, 2022
    affected < 32:9.16.23-0.9.el8.1fixed 32:9.16.23-0.9.el8.1

    BIND 9.16.11 -> 9.16.26, 9.17.0 -> 9.18.0 and versions 9.16.11-S1 -> 9.16.26-S1 of the BIND Supported Preview Edition. Specifically crafted TCP streams can cause connections to BIND to remain in CLOSE_WAIT status for an indefinite period of time, even after the client has termina

Page 2 of 2