[Debian] High CVE: CVE-2023-4408/CVE-2023-5517/.../CVE-2023-50868/CVE-2023-6516 bind9 : multiple CVEs

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

Bug Description

CVE-2023-4408: https://nvd.nist.gov/vuln/detail/CVE-2023-4408

The DNS message parsing code in `named` includes a section whose computational complexity is overly high. It does not cause problems for typical DNS traffic, but crafted queries and responses may cause excessive CPU load on the affected `named` instance by exploiting this flaw. This issue affects both authoritative servers and recursive resolvers. This issue affects BIND 9 versions 9.0.0 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.9.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.

CVE-2023-5517: https://nvd.nist.gov/vuln/detail/CVE-2023-5517

A flaw in query-handling code can cause `named` to exit prematurely with an assertion failure when: - `nxdomain-redirect <domain>;` is configured, and - the resolver receives a PTR query for an RFC 1918 address that would normally result in an authoritative NXDOMAIN response. This issue affects BIND 9 versions 9.12.0 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.8-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.

CVE-2023-5679: https://nvd.nist.gov/vuln/detail/CVE-2023-5679

A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure during recursive resolution, when both of these features are enabled. This issue affects BIND 9 versions 9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.12-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.

CVE-2023-50387: https://nvd.nist.gov/vuln/detail/CVE-2023-50387

Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.

CVE-2023-50868: https://nvd.nist.gov/vuln/detail/CVE-2023-50868

The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 5155 specification implies that an algorithm must perform thousands of iterations of a hash function in certain situations.

CVE-2023-6516: https://nvd.nist.gov/vuln/detail/CVE-2023-6516

To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to clean up the database. It uses several methods, including some that are asynchronous: a small chunk of memory pointing to the cache element that can be cleaned up is first allocated and then queued for later processing. It was discovered that if the resolver is continuously processing query patterns triggering this type of cache-database maintenance, `named` may not be able to handle the cleanup events in a timely manner. This in turn enables the list of queued cleanup events to grow infinitely large over time, allowing the configured `max-cache-size` limit to be significantly exceeded. This issue affects BIND 9 versions 9.16.0 through 9.16.45 and 9.16.8-S1 through 9.16.45-S1.

Base Score: High

Reference:

['bind9-dnsutils_1:9.16.44-1~deb11u1_amd64.deb===>bind9-dnsutils_1:9.16.48-1_amd64.deb', 'bind9-host_1:9.16.44-1~deb11u1_amd64.deb===>bind9-host_1:9.16.48-1_amd64.deb', 'bind9-libs_1:9.16.44-1~deb11u1_amd64.deb===>bind9-libs_1:9.16.48-1_amd64.deb']
https://security-tracker.debian.org/tracker/DSA-5621-1

Peng Zhang (pzhang2)
Changed in starlingx:
assignee: nobody → Peng Zhang (pzhang2)
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/+/910141

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/+/910141
Committed: https://opendev.org/starlingx/tools/commit/e819e5f1443b2df796fe07603dc270cbf1b00870
Submitter: "Zuul (22348)"
Branch: master

commit e819e5f1443b2df796fe07603dc270cbf1b00870
Author: Peng Zhang <email address hidden>
Date: Wed Feb 21 07:37:15 2024 +0000

    bind9: Upgrade to 1:9.16.48-1

    Upgrade package bind9-dnsutils, bind9-host and bind9-libs from
    1:9.16.44-1~deb11u1 to 1:9.16.48-1 in order to fixing following
    CVE issues:
    1.CVE-2023-4408
    2.CVE-2023-5517
    3.CVE-2023-5679
    4.CVE-2023-50387
    5.CVE-2023-50868
    6.CVE-2023-6516.

    Refer to:
    https://nvd.nist.gov/vuln/detail/CVE-2023-4408
    https://nvd.nist.gov/vuln/detail/CVE-2023-5517
    https://nvd.nist.gov/vuln/detail/CVE-2023-5679
    https://nvd.nist.gov/vuln/detail/CVE-2023-50387
    https://nvd.nist.gov/vuln/detail/CVE-2023-50868
    https://nvd.nist.gov/vuln/detail/CVE-2023-6516
    https://security-tracker.debian.org/tracker/DSA-5621-1

    TestPlan:
    PASS: downloader; build-pkgs; build-image
    PASS: Jenkins Installation

    Closes-Bug: 2054275

    Change-Id: Ia672dfd46b71db404dee55a8a33e66a7d3580791
    Signed-off-by: Peng Zhang <email address hidden>

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.