Описание
A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0) may exit with an assertion failure, resulting in a denial of service. To be vulnerable, the BIND server must allow recursive queries and have at least two RPZ zones configured: one with the default setting of "recursive-only yes", and the other with "recursive-only no".
This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1.
A flaw was found in BIND. A remote attacker can cause a denial of service (DoS) by sending a sequence of recursive and non-recursive queries to an affected server. When BIND is configured to handle recursive queries alongside multiple Response Policy Zones (RPZ) with differing recursion settings, processing these queries triggers an assertion failure. This failure causes the service to crash and terminate abruptly.
Отчет
Red Hat rates this vulnerability as Important because an unauthenticated remote attacker can crash the BIND name service, causing a denial of service for all dependent infrastructure. Exploitation requires a specific, non-default deployment where recursive queries are permitted alongside multiple response policy zones configured with conflicting recursive-only options. Default Red Hat Enterprise Linux configurations do not define response policy zones and are therefore not exposed unless administrators have explicitly implemented this combination of policies.
Меры по смягчению последствий
Ensure all Response Policy Zones (RPZ) configured in /etc/named.conf use identical recursive-only settings. For example, ensure all RPZ definitions consistently specify recursive-only yes; or recursive-only no;, eliminating conflicting policies.
Alternatively, limit recursive query privileges strictly to authorized clients by configuring the allow-recursion option with an access control list (ACL).
After modifying the configuration, validate the syntax and reload the service:
Caveats:
Aligning the recursive-only setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.
Warning:
Reloading or restarting the named service may cause a momentary pause in active DNS query processing.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 6 | bind | Not affected | ||
| Red Hat Enterprise Linux 7 | bind | Not affected | ||
| Red Hat Enterprise Linux 8 | bind | Not affected | ||
| Red Hat Enterprise Linux 9 | dhcp | Affected | ||
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-training-operator-rhel9 | Not affected | ||
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Affected | ||
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Affected | ||
| Red Hat Enterprise Linux 10 | bind | Fixed | RHSA-2026:92419 | 29.10.2026 |
| Red Hat Enterprise Linux 10 | bind | Fixed | RHSA-2026:98637 | 11.11.2026 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | bind | Fixed | RHSA-2026:94115 | 03.11.2026 |
Показывать по
Дополнительная информация
Статус:
EPSS
7.5 High
CVSS3
Связанные уязвимости
A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0) may exit with an assertion failure, resulting in a denial of service. To be vulnerable, the BIND server must allow recursive queries and have at least two RPZ zones configured: one with the default setting of "recursive-only yes", and the other with "recursive-only no". This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1.
A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0) may exit with an assertion failure, resulting in a denial of service. To be vulnerable, the BIND server must allow recursive queries and have at least two RPZ zones configured: one with the default setting of "recursive-only yes", and the other with "recursive-only no". This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1.
Specific RPZ configurations and query patterns may result in an unexpected exit
A recursive BIND server that receives a query with recursion desired ( ...
A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0) may exit with an assertion failure, resulting in a denial of service. To be vulnerable, the BIND server must allow recursive queries and have at least two RPZ zones configured: one with the default setting of "recursive-only yes", and the other with "recursive-only no". This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1.
EPSS
7.5 High
CVSS3