Описание
If a named
caching resolver is configured with serve-stale-enable
yes
, and with stale-answer-client-timeout
set to 0
(the only allowable value other than disabled
), and if the resolver, in the process of resolving a query, encounters a CNAME chain involving a specific combination of cached or authoritative records, the daemon will abort with an assertion failure. This issue affects BIND 9 versions 9.20.0 through 9.20.10, 9.21.0 through 9.21.9, and 9.20.9-S1 through 9.20.10-S1.
Релиз | Статус | Примечание |
---|---|---|
devel | released | 1:9.20.11-1ubuntu1 |
esm-infra-legacy/trusty | not-affected | |
esm-infra/bionic | not-affected | |
esm-infra/focal | not-affected | |
esm-infra/xenial | not-affected | |
jammy | not-affected | 1:9.18.30-0ubuntu0.22.04.2 |
noble | not-affected | 1:9.18.30-0ubuntu0.24.04.2 |
plucky | released | 1:9.20.4-3ubuntu1.2 |
upstream | released | 9.20.11,9.21.10 |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
devel | DNE | |
esm-infra/focal | not-affected | 9.20+ only |
jammy | not-affected | 9.20+ only |
noble | DNE | |
plucky | DNE | |
upstream | needs-triage |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
devel | not-affected | 9.20+ only |
esm-apps/noble | not-affected | 9.20+ only |
esm-infra-legacy/trusty | not-affected | code not present |
esm-infra/bionic | not-affected | 9.20+ only |
esm-infra/focal | not-affected | code not present |
esm-infra/xenial | not-affected | code not present |
jammy | not-affected | code not present |
noble | not-affected | 9.20+ only |
plucky | not-affected | 9.20+ only |
upstream | needs-triage |
Показывать по
EPSS
7.5 High
CVSS3
Связанные уязвимости
If a `named` caching resolver is configured with `serve-stale-enable` `yes`, and with `stale-answer-client-timeout` set to `0` (the only allowable value other than `disabled`), and if the resolver, in the process of resolving a query, encounters a CNAME chain involving a specific combination of cached or authoritative records, the daemon will abort with an assertion failure. This issue affects BIND 9 versions 9.20.0 through 9.20.10, 9.21.0 through 9.21.9, and 9.20.9-S1 through 9.20.10-S1.
If a `named` caching resolver is configured with `serve-stale-enable` `yes`, and with `stale-answer-client-timeout` set to `0` (the only allowable value other than `disabled`), and if the resolver, in the process of resolving a query, encounters a CNAME chain involving a specific combination of cached or authoritative records, the daemon will abort with an assertion failure. This issue affects BIND 9 versions 9.20.0 through 9.20.10, 9.21.0 through 9.21.9, and 9.20.9-S1 through 9.20.10-S1.
If a `named` caching resolver is configured with `serve-stale-enable` ...
If a `named` caching resolver is configured with `serve-stale-enable` `yes`, and with `stale-answer-client-timeout` set to `0` (the only allowable value other than `disabled`), and if the resolver, in the process of resolving a query, encounters a CNAME chain involving a specific combination of cached or authoritative records, the daemon will abort with an assertion failure. This issue affects BIND 9 versions 9.20.0 through 9.20.10, 9.21.0 through 9.21.9, and 9.20.9-S1 through 9.20.10-S1.
EPSS
7.5 High
CVSS3