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. The scope of this vulnerability is limited 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.
Created bind tracking bugs for this issue: Affects: fedora-all [bug 2164506]
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2023:2261 https://access.redhat.com/errata/RHSA-2023:2261
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2023:2792 https://access.redhat.com/errata/RHSA-2023:2792
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2022-3094
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2023:7177 https://access.redhat.com/errata/RHSA-2023:7177
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Extended Update Support Via RHSA-2024:1406 https://access.redhat.com/errata/RHSA-2024:1406
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Extended Update Support Via RHSA-2024:2720 https://access.redhat.com/errata/RHSA-2024:2720