# CVE-2024-11187: Many records in the additional section cause CPU exhaustion > Attackers can cause CPU exhaustion in BIND servers by sending crafted queries that generate excessive additional section records. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 29 Jan 2025 - **Updated:** 11 Feb 2025 - **Also known as:** ALPINE-CVE-2024-11187, ALSA-2025:1675, ALSA-2025:1676, ALSA-2025:1681, AZL-56093, AZL-56097, AZL-56198, BELL-CVE-2024-11187, CLSA-2025-1740823520, CLSA-2025-1740823729, CLSA-2025-1740823970, CLSA-2025-1741126041, CLSA-2025-1741216108, CLSA-2025-1741216137, CLSA-2025-1741216880, CLSA-2025-1741624657, DEBIAN-CVE-2024-11187, DLA-4050-1, GHSA-w8w2-83mf-6cp5, OESA-2025-1172, OESA-2025-1215, OESA-2025-1341, OESA-2025-1558, RHSA-2025:1664, RHSA-2025:1665, RHSA-2025:1666, RHSA-2025:1669, RHSA-2025:1674, RHSA-2025:1675, RHSA-2025:1676, RHSA-2025:1678, RHSA-2025:1679, RHSA-2025:1681, RHSA-2025:1684, RHSA-2025:1685, RHSA-2025:1687, RHSA-2025:1691, RHSA-2025:1718, RLSA-2025:1675, RLSA-2025:1676, RLSA-2025:1681, SUSE-SU-2025:0337-1, SUSE-SU-2025:0359-1, SUSE-SU-2025:0384-1, SUSE-SU-2025:0389-1, SUSE-SU-2025:0427-1, UBUNTU-CVE-2024-11187 ## What is CVE-2024-11187? CVE-2024-11187 is a high-severity denial of service vulnerability in ISC BIND 9, published on 29 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-405 (Asymmetric Resource Consumption (Amplification)) ## Which versions are affected by CVE-2024-11187? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `bind` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-chroot` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-devel` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-export-devel` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-export-libs` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-libs` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-libs-lite` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-license` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-lite-devel` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-pkcs11` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-pkcs11-devel` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-pkcs11-libs` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-pkcs11-utils` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-sdb` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-sdb-chroot` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind-utils` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `bind9.16` | AlmaLinux:8 | All versions | 32:9.16.23-0.22.el8_10.2 | | `bind9.16-chroot` | AlmaLinux:8 | All versions | 32:9.16.23-0.22.el8_10.2 | | `bind9.16-devel` | AlmaLinux:8 | All versions | 32:9.16.23-0.22.el8_10.2 | | `bind9.16-dnssec-utils` | AlmaLinux:8 | All versions | 32:9.16.23-0.22.el8_10.2 | | `bind9.16-doc` | AlmaLinux:8 | All versions | 32:9.16.23-0.22.el8_10.2 | | `bind9.16-libs` | AlmaLinux:8 | All versions | 32:9.16.23-0.22.el8_10.2 | | `bind9.16-license` | AlmaLinux:8 | All versions | 32:9.16.23-0.22.el8_10.2 | | `bind9.16-utils` | AlmaLinux:8 | All versions | 32:9.16.23-0.22.el8_10.2 | | `python3-bind` | AlmaLinux:8 | All versions | 32:9.11.36-16.el8_10.4 | | `python3-bind9.16` | AlmaLinux:8 | All versions | 32:9.16.23-0.22.el8_10.2 | | `bind` | AlmaLinux:9 | All versions | 32:9.16.23-24.el9_5.3 | | `bind-chroot` | AlmaLinux:9 | All versions | 32:9.16.23-24.el9_5.3 | | `bind-devel` | AlmaLinux:9 | All versions | 32:9.16.23-24.el9_5.3 | | `bind-dnssec-doc` | AlmaLinux:9 | All versions | 32:9.16.23-24.el9_5.3 | | `bind-dnssec-utils` | AlmaLinux:9 | All versions | 32:9.16.23-24.el9_5.3 | | `bind-doc` | AlmaLinux:9 | All versions | 32:9.16.23-24.el9_5.3 | | `bind-libs` | AlmaLinux:9 | All versions | 32:9.16.23-24.el9_5.3 | | `bind-license` | AlmaLinux:9 | All versions | 32:9.16.23-24.el9_5.3 | | `bind-utils` | AlmaLinux:9 | All versions | 32:9.16.23-24.el9_5.3 | | `python3-bind` | AlmaLinux:9 | All versions | 32:9.16.23-24.el9_5.3 | | `bind` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-16.el8_10.4 | | `bind-chroot` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-16.el8_10.4 | | `bind-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-16.el8_10.4 | | `bind-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-16.el8_10.4 | ## How do I fix CVE-2024-11187? Upgrade to a fixed version. ## Is CVE-2024-11187 being exploited? There is no known exploitation of CVE-2024-11187 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-11187 and fix it if it is affected. What it is: CVE-2024-11187 is a high-severity denial of service vulnerability in ISC BIND 9, published on 29 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-11187 in the wild and no public exploit code. Affected product: ISC BIND 9. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-11187/ (Markdown: https://insights.sbomify.com/CVE-2024-11187/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-11187 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-11187 - OSV: https://osv.dev/vulnerability/CVE-2024-11187 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-11187/ Summaries are generated and may contain mistakes; the official description above is the record.