# CVE-2021-25215: Denial of service in BIND9 > Remote attackers can cause the BIND DNS server to crash by sending specific queries for DNAME records, resulting in a denial of service. - **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 Apr 2021 - **Updated:** 16 Sep 2024 - **Also known as:** ALPINE-CVE-2021-25215, DEBIAN-CVE-2021-25215, GHSA-r4mp-379r-9756, RHSA-2021:1468, RHSA-2021:1469, RHSA-2021:1475, RHSA-2021:1476, RHSA-2021:1477, RHSA-2021:1478, RHSA-2021:1479, RHSA-2021:1989, RHSA-2021:2024, RHSA-2021:2028, RLSA-2021:1989, UBUNTU-CVE-2021-25215 ## What is CVE-2021-25215? CVE-2021-25215 is a high-severity denial of service vulnerability in Debian Debian Linux, published on 29 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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 query for a record triggering the flaw described above, the named process will terminate due to a failed assertion check. The vulnerability affects all currently maintained BIND 9 branches (9.11, 9.11-S, 9.16, 9.16-S, 9.17) as well as all other versions of BIND 9. Weakness: CWE-617 (Reachable Assertion) ## Which versions are affected by CVE-2021-25215? It affects 16 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `bind` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-chroot` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-devel` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-export-devel` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-export-libs` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-libs` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-libs-lite` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-license` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-lite-devel` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-pkcs11` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-pkcs11-devel` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-pkcs11-libs` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-pkcs11-utils` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-sdb` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-sdb-chroot` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-utils` | Red Hat:enterprise_linux:7::client | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind` | Red Hat:enterprise_linux:7::computenode | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-chroot` | Red Hat:enterprise_linux:7::computenode | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-export-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-lite-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-pkcs11` | Red Hat:enterprise_linux:7::computenode | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-pkcs11-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-pkcs11-libs` | Red Hat:enterprise_linux:7::computenode | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-pkcs11-utils` | Red Hat:enterprise_linux:7::computenode | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-sdb` | Red Hat:enterprise_linux:7::computenode | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-sdb-chroot` | Red Hat:enterprise_linux:7::computenode | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind` | Red Hat:enterprise_linux:7::server | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-chroot` | Red Hat:enterprise_linux:7::server | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-devel` | Red Hat:enterprise_linux:7::server | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-export-devel` | Red Hat:enterprise_linux:7::server | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-export-libs` | Red Hat:enterprise_linux:7::server | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-libs` | Red Hat:enterprise_linux:7::server | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-libs-lite` | Red Hat:enterprise_linux:7::server | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-license` | Red Hat:enterprise_linux:7::server | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-lite-devel` | Red Hat:enterprise_linux:7::server | All versions | 32:9.11.4-26.P2.el7_9.5 | | `bind-pkcs11` | Red Hat:enterprise_linux:7::server | All versions | 32:9.11.4-26.P2.el7_9.5 | Products: Debian Debian Linux, Fedoraproject Fedora, Isc Bind, Netapp 500f Firmware, Netapp A250 Firmware, Netapp Active Iq Unified Manager, Netapp Cloud Backup, Netapp H300e Firmware, Netapp H300s Firmware, Netapp H410s Firmware, Netapp H500e Firmware, Netapp H500s Firmware, Netapp H700e Firmware, Netapp H700s Firmware, Oracle Tekelec Platform Distribution, Siemens Sinec Infrastructure Network Services. ## How do I fix CVE-2021-25215? Upgrade to a fixed version. ## Is CVE-2021-25215 being exploited? There is no known exploitation of CVE-2021-25215 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-25215 and fix it if it is affected. What it is: CVE-2021-25215 is a high-severity denial of service vulnerability in Debian Debian Linux, published on 29 Apr 2021. 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-2021-25215 in the wild and no public exploit code. Affected product: Debian Debian Linux. 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-2021-25215/ (Markdown: https://insights.sbomify.com/CVE-2021-25215/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-25215 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-25215 - OSV: https://osv.dev/vulnerability/CVE-2021-25215 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-25215/ Summaries are generated and may contain mistakes; the official description above is the record.