Описание
If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server replies with a valid wildcard answer and signed NSEC3 proof, followed by an unsigned NSEC at the same owner name, it will trigger an unexpected program exit.
This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
A flaw was found in BIND. A remote attacker, by sending a specially crafted DNSSEC-signed authoritative zone reply, can trigger an unexpected program exit in the validating resolver. This can lead to a Denial of Service (DoS) for the affected BIND resolver.
Отчет
This is an Important denial of service vulnerability in BIND resolvers. When DNSSEC validation is enabled, a specially crafted DNSSEC reply from an authoritative server can cause the BIND resolver to unexpectedly exit, leading to a disruption of DNS resolution services. This impacts the availability of DNS resolution on affected Red Hat systems configured with DNSSEC.
Меры по смягчению последствий
To mitigate this issue, disable DNSSEC validation in the BIND resolver configuration. This can be achieved by setting dnssec-enable no; and dnssec-validation no; within the options block in named.conf or an included configuration file. A restart of the named service is required for the changes to take effect and may impact DNS resolution during the restart. Disabling DNSSEC validation will reduce the security posture of DNS resolution by removing integrity protection for DNS data.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 6 | bind | Not affected | ||
| Red Hat Enterprise Linux 9 | dhcp | 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:75577 | 05.10.2026 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | bind | Fixed | RHSA-2026:94115 | 03.11.2026 |
| Red Hat Enterprise Linux 7 Extended Lifecycle Support | bind | Fixed | RHSA-2026:95726 | 06.11.2026 |
| Red Hat Enterprise Linux 8 | bind9.16 | Fixed | RHSA-2026:79113 | 08.10.2026 |
| Red Hat Enterprise Linux 8 | bind | Fixed | RHSA-2026:79162 | 08.10.2026 |
| Red Hat Enterprise Linux 8 | bind | Fixed | RHSA-2026:79162 | 08.10.2026 |
Показывать по
Дополнительная информация
Статус:
7.5 High
CVSS3
Связанные уязвимости
If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server replies with a valid wildcard answer and signed NSEC3 proof, followed by an unsigned NSEC at the same owner name, it will trigger an unexpected program exit. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server replies with a valid wildcard answer and signed NSEC3 proof, followed by an unsigned NSEC at the same owner name, it will trigger an unexpected program exit. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Validating resolver can abort while caching a mismatched NOQNAME proof
If a BIND resolver sends a query for a DNSSEC-signed authoritative zon ...
If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server replies with a valid wildcard answer and signed NSEC3 proof, followed by an unsigned NSEC at the same owner name, it will trigger an unexpected program exit. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
7.5 High
CVSS3