Описание
ELSA-2023-2261: bind security and bug fix update (MODERATE)
[32:9.16.23-11]
- Correct backport issue in statistics rendering fix (#2126912)
[32:9.16.23-10]
- Handle subtle difference between upstream and rhel (CVE-2022-3094)
[32:9.16.23-9]
- Prevent flooding with UPDATE requests (CVE-2022-3094)
- Handle RRSIG queries when server-stale is active (CVE-2022-3736)
- Fix crash when soft-quota is reached and serve-stale is active (CVE-2022-3924)
[32:9.16.23-8]
- Correct regression preventing bind-dyndb-ldap build (#2162795)
[32:9.16.23-7]
- Prevent freeing zone during statistics rendering (#2101712)
[32:9.16.23-6]
- Bound the amount of work performed for delegations (CVE-2022-2795)
- Add /usr/lib64/named to bind-chroot (#2129466)
Обновленные пакеты
Oracle Linux 9
Oracle Linux aarch64
bind
9.16.23-11.el9
bind-chroot
9.16.23-11.el9
bind-devel
9.16.23-11.el9
bind-dnssec-doc
9.16.23-11.el9
bind-dnssec-utils
9.16.23-11.el9
bind-doc
9.16.23-11.el9
bind-libs
9.16.23-11.el9
bind-license
9.16.23-11.el9
bind-utils
9.16.23-11.el9
python3-bind
9.16.23-11.el9
Oracle Linux x86_64
bind
9.16.23-11.el9
bind-chroot
9.16.23-11.el9
bind-devel
9.16.23-11.el9
bind-dnssec-doc
9.16.23-11.el9
bind-dnssec-utils
9.16.23-11.el9
bind-doc
9.16.23-11.el9
bind-libs
9.16.23-11.el9
bind-license
9.16.23-11.el9
bind-utils
9.16.23-11.el9
python3-bind
9.16.23-11.el9
Связанные CVE
Связанные уязвимости
ELSA-2023-2792: bind9.16 security and bug fix update (MODERATE)
This issue can affect BIND 9 resolvers with `stale-answer-enable yes;` that also make use of the option `stale-answer-client-timeout`, configured with a value greater than zero. If the resolver receives many queries that require recursion, there will be a corresponding increase in the number of clients that are waiting for recursion to complete. If there are sufficient clients already waiting when a new client query is received so that it is necessary to SERVFAIL the longest waiting client (see BIND 9 ARM `recursive-clients` limit and soft quota), then it is possible for a race to occur between providing a stale answer to this older client and sending an early timeout SERVFAIL, which may cause an assertion failure. This issue affects BIND 9 versions 9.16.12 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 through 9.19.8, and 9.16.12-S1 through 9.16.36-S1.
This issue can affect BIND 9 resolvers with `stale-answer-enable yes;` that also make use of the option `stale-answer-client-timeout`, configured with a value greater than zero. If the resolver receives many queries that require recursion, there will be a corresponding increase in the number of clients that are waiting for recursion to complete. If there are sufficient clients already waiting when a new client query is received so that it is necessary to SERVFAIL the longest waiting client (see BIND 9 ARM `recursive-clients` limit and soft quota), then it is possible for a race to occur between providing a stale answer to this older client and sending an early timeout SERVFAIL, which may cause an assertion failure. This issue affects BIND 9 versions 9.16.12 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 through 9.19.8, and 9.16.12-S1 through 9.16.36-S1.
This issue can affect BIND 9 resolvers with `stale-answer-enable yes;` that also make use of the option `stale-answer-client-timeout`, configured with a value greater than zero. If the resolver receives many queries that require recursion, there will be a corresponding increase in the number of clients that are waiting for recursion to complete. If there are sufficient clients already waiting when a new client query is received so that it is necessary to SERVFAIL the longest waiting client (see BIND 9 ARM `recursive-clients` limit and soft quota), then it is possible for a race to occur between providing a stale answer to this older client and sending an early timeout SERVFAIL, which may cause an assertion failure. This issue affects BIND 9 versions 9.16.12 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 through 9.19.8, and 9.16.12-S1 through 9.16.36-S1.