Описание
ELSA-2023-2792: bind9.16 security and bug fix update (MODERATE)
[32:9.16.23-0.14]
- Handle subtle difference between upstream and rhel (CVE-2022-3094)
[32:9.16.23-0.13]
- 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-0.12]
- Include bind9.16-dnssec-utils in public repository (#2115322)
[32:9.16.23-0.11]
- Bound the amount of work performed for delegations (CVE-2022-2795)
[32:9.16.23-0.10]
- Fix possible serve-stale related crash (CVE-2022-3080)
- Fix memory leak in ECDSA verify processing (CVE-2022-38177)
- Fix memory leak in EdDSA verify processing (CVE-2022-38178)
Обновленные пакеты
Oracle Linux 8
Oracle Linux aarch64
bind9.16
9.16.23-0.14.el8
bind9.16-chroot
9.16.23-0.14.el8
bind9.16-devel
9.16.23-0.14.el8
bind9.16-dnssec-utils
9.16.23-0.14.el8
bind9.16-doc
9.16.23-0.14.el8
bind9.16-libs
9.16.23-0.14.el8
bind9.16-license
9.16.23-0.14.el8
bind9.16-utils
9.16.23-0.14.el8
python3-bind9.16
9.16.23-0.14.el8
Oracle Linux x86_64
bind9.16
9.16.23-0.14.el8
bind9.16-chroot
9.16.23-0.14.el8
bind9.16-devel
9.16.23-0.14.el8
bind9.16-dnssec-utils
9.16.23-0.14.el8
bind9.16-doc
9.16.23-0.14.el8
bind9.16-libs
9.16.23-0.14.el8
bind9.16-license
9.16.23-0.14.el8
bind9.16-utils
9.16.23-0.14.el8
python3-bind9.16
9.16.23-0.14.el8
Связанные CVE
Связанные уязвимости
ELSA-2023-2261: bind security and bug fix update (MODERATE)
Sending a flood of dynamic DNS updates may cause `named` to allocate large amounts of memory. This, in turn, may cause `named` to exit due to a lack of free memory. We are not aware of any cases where this has been exploited. Memory is allocated prior to the checking of access permissions (ACLs) and is retained during the processing of a dynamic update from a client whose access credentials are accepted. Memory allocated to clients that are not permitted to send updates is released immediately upon rejection. The scope of this vulnerability is limited therefore to trusted clients who are permitted to make dynamic zone changes. If a dynamic update is REFUSED, memory will be released again very quickly. Therefore it is only likely to be possible to degrade or stop `named` by sending a flood of unaccepted dynamic updates comparable in magnitude to a query flood intended to achieve the same detrimental outcome. BIND 9.11 and earlier branches are also affected, but through exhaustion of ...
Sending a flood of dynamic DNS updates may cause `named` to allocate large amounts of memory. This, in turn, may cause `named` to exit due to a lack of free memory. We are not aware of any cases where this has been exploited. Memory is allocated prior to the checking of access permissions (ACLs) and is retained during the processing of a dynamic update from a client whose access credentials are accepted. Memory allocated to clients that are not permitted to send updates is released immediately upon rejection. The scope of this vulnerability is limited therefore to trusted clients who are permitted to make dynamic zone changes. If a dynamic update is REFUSED, memory will be released again very quickly. Therefore it is only likely to be possible to degrade or stop `named` by sending a flood of unaccepted dynamic updates comparable in magnitude to a query flood intended to achieve the same detrimental outcome. BIND 9.11 and earlier branches are also affected, but through exhaustion of ...
Sending a flood of dynamic DNS updates may cause `named` to allocate large amounts of memory. This, in turn, may cause `named` to exit due to a lack of free memory. We are not aware of any cases where this has been exploited. Memory is allocated prior to the checking of access permissions (ACLs) and is retained during the processing of a dynamic update from a client whose access credentials are accepted. Memory allocated to clients that are not permitted to send updates is released immediately upon rejection. The scope of this vulnerability is limited therefore to trusted clients who are permitted to make dynamic zone changes. If a dynamic update is REFUSED, memory will be released again very quickly. Therefore it is only likely to be possible to degrade or stop `named` by sending a flood of unaccepted dynamic updates comparable in magnitude to a query flood intended to achieve the same detrimental outcome. BIND 9.11 and earlier branches are also affected, but through exhaustion of