CVE-2024-12705

Clients using DNS-over-HTTPS (DoH) can exhaust a DNS resolver's CPU and/or memory by flooding it with crafted valid or invalid HTTP/2 traffic. This issue affects BIND 9 versions 9.18.0 through 9.18.32, 9.20.0 through 9.20.4, 9.21.0 through 9.21.3, and 9.18.11-S1 through 9.18.32-S1.

BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly.

Security Fix(es):

It is possible to construct a zone such that some queries to it will generate responses containing numerous records in the Additional section. An attacker sending many such queries can cause either the authoritative server itself or an independent resolver to use disproportionate resources processing the queries. Zones will usually need to have been deliberately crafted to attack this exposure. This issue affects BIND 9 versions 9.11.0 through 9.11.37, 9.16.0 through 9.16.50, 9.18.0 through 9.18.32, 9.20.0 through 9.20.4, 9.21.0 through 9.21.3, 9.11.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.50-S1, and 9.18.11-S1 through 9.18.32-S1.(CVE-2024-11187)

Clients using DNS-over-HTTPS (DoH) can exhaust a DNS resolver's CPU and/or memory by flooding it with crafted valid or invalid HTTP/2 traffic. This issue affects BIND 9 versions 9.18.0 through 9.18.32, 9.20.0 through 9.20.4, 9.21.0 through 9.21.3, and 9.18.11-S1 through 9.18.32-S1.(CVE-2024-12705)

BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly.

Security Fix(es):

It is possible to construct a zone such that some queries to it will generate responses containing numerous records in the Additional section. An attacker sending many such queries can cause either the authoritative server itself or an independent resolver to use disproportionate resources processing the queries. Zones will usually need to have been deliberately crafted to attack this exposure. This issue affects BIND 9 versions 9.11.0 through 9.11.37, 9.16.0 through 9.16.50, 9.18.0 through 9.18.32, 9.20.0 through 9.20.4, 9.21.0 through 9.21.3, 9.11.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.50-S1, and 9.18.11-S1 through 9.18.32-S1.(CVE-2024-11187)

Clients using DNS-over-HTTPS (DoH) can exhaust a DNS resolver's CPU and/or memory by flooding it with crafted valid or invalid HTTP/2 traffic. This issue affects BIND 9 versions 9.18.0 through 9.18.32, 9.20.0 through 9.20.4, 9.21.0 through 9.21.3, and 9.18.11-S1 through 9.18.32-S1.(CVE-2024-12705)

Clients using DNS-over-HTTPS (DoH) can exhaust a DNS resolver's CPU and/or memory by flooding it with crafted valid or invalid HTTP/2 traffic. This issue affects BIND 9 versions 9.18.0 through 9.18.32, 9.20.0 through 9.20.4, 9.21.0 through 9.21.3, and 9.18.11-S1 through 9.18.32-S1.

BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly.

Security Fix(es):

• bind: bind9: Many records in the additional section cause CPU exhaustion (CVE-2024-11187)
• bind: bind9: DNS-over-HTTPS implementation suffers from multiple issues under heavy query load (CVE-2024-12705)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Clients using DNS-over-HTTPS (DoH) can exhaust a DNS resolver's CPU and/or memory by flooding it with crafted valid or invalid HTTP/2 traffic. This issue affects BIND 9 versions 9.18.0 through 9.18.32, 9.20.0 through 9.20.4, 9.21.0 through 9.21.3, and 9.18.11-S1 through 9.18.32-S1.

Clients using DNS-over-HTTPS (DoH) can exhaust a DNS resolver's CPU and/or memory by flooding it with crafted valid or invalid HTTP/2 traffic. This issue affects BIND 9 versions 9.18.0 through 9.18.32, 9.20.0 through 9.20.4, 9.21.0 through 9.21.3, and 9.18.11-S1 through 9.18.32-S1.

Many records in the additional section cause CPU exhaustion. (CVE-2024-11187) DNS-over-HTTPS implementation suffers from multiple issues under heavy query load. (CVE-2024-12705)

These are all security issues fixed in the bind-9.20.5-1.1 package on the GA media of openSUSE Tumbleweed.

BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly.

Security Fix(es):

• bind: bind9: Many records in the additional section cause CPU exhaustion (CVE-2024-11187)

• bind: bind9: DNS-over-HTTPS implementation suffers from multiple issues under heavy query load (CVE-2024-12705)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

This update for bind fixes the following issues:

Update to version 9.20.9.

• Security issues fixed:

  • CVE-2025-40775: denial-of-service due to assertion failure caused by the processing of a NS message with an invalid TSIG (bsc#1243361).
  • CVE-2024-12705: CPU and memory exhaustion due to DNS-over-HTTPS issues that arise under heavy query load (bsc#1236597).
  • CVE-2024-11187: CPU exhaustion when processing queries that lead to responses containing several records in the Additional data section (bsc#1236596).

• Changelog:

  • Feature changes:

    • Performance optimization for NSEC3 lookups introduced in BIND 9.20.2 was reverted to avoid risks associated with a complex code change.
    • The configuration clauses parental-agents and primaries are renamed to remote-servers.
    • Add none parameter to query-source and query-source-v6 to disable IPv4 or IPv6 upstream queries but allow listening to queries from clients on IPv4 or IPv6.
    • dnssec-ksr now supports KSK rollovers.
    • Print RFC 7314: EXPIRE option in transfer summary.
    • Emit more helpful log messages for exceeding max-records-per-type.
    • Harden key management when key files have become unavailable.

  • New Features:

    • Add support for EDE 20 (Not Authoritative).
    • Add support for EDE 7 and EDE 8.
    • dig can now display the received BADVERS message during negotiation.
    • Add an rndc command to reset some statistics counters.
    • Implement the min-transfer-rate-in configuration option.
    • Add HTTPS record query to host command line tool.
    • Implement sig0key-checks-limit and sig0message-checks-limit.
    • Adds support for EDE code 1 and 2.
    • Add an rndc command to toggle jemalloc profiling.
    • Add support for multiple extended DNS errors.
    • Print the expiration time of stale records.
    • Add Extended DNS Error Code 22 - No Reachable Authority.
    • Add a new option to configure the maximum number of outgoing queries per client request.
    • Use the Server Name Indication (SNI) extension for all outgoing TLS connections.
    • Update built-in bind.keys file with the new 2025 IANA root key.
    • Add an initial-ds entry to bind.keys for the new root key, ID 38696, which is scheduled for publication in January 2025.

  • Bug Fixes:

    • Restore NSEC3 closest-encloser lookup improvements.
    • Stop caching lack of EDNS support.
    • Fix resolver statistics counters for timed-out responses.
    • Nested DNS validation could cause an assertion failure.
    • Wait for memory reclamation to finish in named-checkconf.
    • Ensure max-clients-per-query is at least clients-per-query.
    • Fix write after free in validator code.
    • Don't enforce NOAUTH/NOCONF flags in DNSKEYs.
    • Fix several small DNSSEC timing issues.
    • Fix inconsistency in CNAME/DNAME handling during resolution.
    • Fix dual-stack-servers configuration option.
    • Fix a data race causing a permanent active client increase.
    • Fix deferred validation of unsigned DS and DNSKEY records.
    • Fix RPZ race condition during a reconfiguration.
    • 'CNAME and other data check' not applied to all types.
    • Relax private DNSKEY and RRSIG constraints.
    • Remove NSEC/DS/NSEC3 RRSIG check from dns_message_parse().
    • Fix TTL issue with ANY queries processed through RPZ 'passthru';.
    • dnssec-signzone needs to check for a NULL key when setting offline.
    • Fix a bug in the statistics channel when querying zone transfer information.
    • Fix assertion failure when dumping recursing clients.
    • Dump the active resolver fetches from dns_resolver_dumpfetches().
    • Recently expired records could be returned with a timestamp in future.
    • YAML string not terminated in negative response in delv.
    • Fix a bug in dnssec-signzone related to keys being offline.
    • Apply the memory limit only to ADB database items.
    • Avoid unnecessary…

This update for bind fixes the following issues:

Update to release 9.18.33

Security Fixes:

• CVE-2024-11187: Fixes CPU exhaustion caused by many records in the additional section (bsc#1236596)
• CVE-2024-12705: Fixes multiple issues in DNS-over-HTTPS implementation when under heavy query load (bsc#1236597)

Toshifumi Sakaguchi discovered that Bind incorrectly handled many records in the additional section. A remote attacker could possibly use this issue to cause Bind to consume CPU resources, leading to a denial of service. (CVE-2024-11187)

Jean-François Billaud discovered that the Bind DNS-over-HTTPS implementation incorrectly handled a heavy query load. A remote attacker could possibly use this issue to cause Bind to consume resources, leading to a denial of service. (CVE-2024-12705)