Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

redhat логотип

CVE-2026-11331

Опубликовано: 22 июл. 2026
Источник: redhat
CVSS3: 7.5
EPSS Низкий

Описание

An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It also may lead to an unexpected exit of the BIND 9 software. This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

A flaw was found in BIND. A remote attacker can send specially crafted, excessively long query names to a resolver configured with Response Policy Zones (RPZ) and wildcard policies. Improper handling of the resulting error condition can cause the service to terminate unexpectedly, leading to a Denial of Service (DoS), or allow the attacker to bypass RPZ security filtering rules.

Отчет

This vulnerability is rated as Important because an unauthenticated remote client can terminate the DNS resolver service or bypass security filtering policies. In default Red Hat Enterprise Linux installations, Response Policy Zones (RPZ) are not configured and require explicit administrative definition. The flaw poses operational risk primarily to recursive resolvers that actively employ wildcard CNAME rules in their policy zones and accept untrusted network queries.

Меры по смягчению последствий

To mitigate this issue, restrict resolver access to trusted networks and avoid using wildcard CNAME entries within Response Policy Zones (RPZ).

  1. Edit /etc/named.conf to limit recursion and query caching to authorized client networks:
acl trusted_clients { 127.0.0.1; 192.168.1.0/24; }; options { allow-recursion { trusted_clients; }; allow-query-cache { trusted_clients; }; };

Additionally, modify RPZ zone files to remove wildcard CNAME statements (such as *.example.com CNAME target.com), replacing them with explicit individual domain entries where feasible. 2. Reload the named service configuration: systemctl reload named Caveats: Restricting query access prevents untrusted external clients from resolving names through the server. Removing wildcard entries means unlisted subdomains will no longer be intercepted by the policy zone until explicit records are added. Warning: Reloading or restarting the named daemon may briefly disrupt ongoing DNS resolution.

Затронутые пакеты

ПлатформаПакетСостояниеРекомендацияРелиз
Red Hat Enterprise Linux 6bindNot affected
Red Hat Enterprise Linux 7bindNot affected
Red Hat Enterprise Linux 8bindNot affected
Red Hat Enterprise Linux 9dhcpNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Affected
Red Hat Enterprise Linux 10bindFixedRHSA-2026:5543717.08.2026
Red Hat Enterprise Linux 10.0 Extended Update SupportbindFixedRHSA-2026:9411503.11.2026
Red Hat Enterprise Linux 8bind9.16FixedRHSA-2026:5450913.08.2026
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Supportbind9.16FixedRHSA-2026:8050112.10.2026

Показывать по

Дополнительная информация

Статус:

Important
Дефект:
CWE-394
https://bugzilla.redhat.com/show_bug.cgi?id=2503721bind: bind: Denial of Service via long query names in RPZ processing

EPSS

Процентиль: 38%
0.00428
Низкий

7.5 High

CVSS3

Связанные уязвимости

CVSS3: 7.5
ubuntu
4 месяца назад

An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It also may lead to an unexpected exit of the BIND 9 software. This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

CVSS3: 7.5
nvd
4 месяца назад

An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It also may lead to an unexpected exit of the BIND 9 software. This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

CVSS3: 7.5
msrc
4 месяца назад

Potential wildcard CNAME RPZ policy bypass

CVSS3: 7.5
debian
4 месяца назад

An attacker who knows (or guesses) that a resolver uses RPZ with wildc ...

CVSS3: 7.5
github
4 месяца назад

An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It also may lead to an unexpected exit of the BIND 9 software. This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

EPSS

Процентиль: 38%
0.00428
Низкий

7.5 High

CVSS3