[Debian] CVE: CVE-2022-3094 / CVE-2022-3736 / CVE-2022-3924: bind: multiple CVEs

Bug #2006410 reported by Yue Tao
256
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
High
hqbai

Bug Description

CVE-2022-3094: https://nvd.nist.gov/vuln/detail/CVE-2022-3094

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 internal resources rather than memory constraints. This may reduce performance but should not be a significant problem for most servers. Therefore we don't intend to address this for BIND versions prior to BIND 9.16. This issue affects BIND 9 versions 9.16.0 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 through 9.19.8, and 9.16.8-S1 through 9.16.36-S1.

CVE-2022-3736: https://nvd.nist.gov/vuln/detail/CVE-2022-3736

BIND 9 resolver can crash when stale cache and stale answers are enabled, option `stale-answer-client-timeout` is set to a positive integer, and the resolver receives an RRSIG query. 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.

CVE-2022-3924: https://nvd.nist.gov/vuln/detail/CVE-2022-3924

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.

Score:
cve_id status cvss3Score av ac pr ui ai
CVE-2022-3094 fixed 7.5 N L N N H
CVE-2022-3736 fixed 7.5 N L N N H

CVE-2022-3924 fixed 7.5 N L N N H

References:

['bind9-dnsutils_1:9.16.33-1~deb11u1_amd64.deb===>bind9-dnsutils_9.16.37-1~deb11u1_amd64.deb', 'bind9-host_1:9.16.33-1~deb11u1_amd64.deb===>bind9-host_9.16.37-1~deb11u1_amd64.deb', 'bind9-libs_1:9.16.33-1~deb11u1_amd64.deb===>bind9-libs_9.16.37-1~deb11u1_amd64.deb']

CVE References

Yue Tao (wrytao)
information type: Public → Public Security
tags: added: stx.8.0 stx.security
Yue Tao (wrytao)
Changed in starlingx:
importance: Undecided → High
assignee: nobody → hqbai (hbai)
status: New → Triaged
Revision history for this message
Ghada Khalil (gkhalil) wrote :

screening: moving to stx.9.0 as current commitment is to only fix CVEs in the stx main branch. The r/stx.8.0 branch has already been created.

tags: added: stx.9.0
removed: stx.8.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tools (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/tools/+/874186

Changed in starlingx:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tools (master)

Reviewed: https://review.opendev.org/c/starlingx/tools/+/874186
Committed: https://opendev.org/starlingx/tools/commit/4630a1cf6edcbd62b571f5295e026ec48bd05cbd
Submitter: "Zuul (22348)"
Branch: master

commit 4630a1cf6edcbd62b571f5295e026ec48bd05cbd
Author: Haiqing Bai <email address hidden>
Date: Fri Feb 17 10:04:38 2023 +0800

    Debian: bind9: Fix 3 CVEs

    Upgrade bind9-dnsutils,bind9-host,bind9-libs from
    "1:9.16.33-1~deb11u1" to "1:9.16.37-1~deb11u1" to
    fix below CVEs:
    CVE-2022-3094
    CVE-2022-3736
    CVE-2022-3924

    Refer to:
    https://security-tracker.debian.org/tracker/DSA-5329-1

    Test Plan:
    a. In builder, run:
       $rm /import/mirrors/starlingx/binaries/bind9*
       $downloader -b
       $repo_manage.py list_pkgs -r deb-local-binary
       Check the required bind9* packages were in the repository
    b. $build-pkgs --clean --parallel 10
       $build-image
       Boot the iso image on board and check that the new
       packages have been installed.

    Closes-Bug: 2006410

    Signed-off-by: Haiqing Bai <email address hidden>
    Change-Id: Ibe03a278b7fbd33403c30003cbed4ad0852ba1b5

Changed in starlingx:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.