Every `named` instance configured to run as a recursive resolver maintains a cache database holding the responses to the queries it has recently sent to authoritative servers. The size limit for that cache database can be configured using the `max-cache-size` statement in the configuration file; it defaults to 90% of the total amount of memory available on the host. When the size of the cache reaches 7/8 of the configured limit, a cache-cleaning algorithm starts to remove expired and/or least-recently used RRsets from the cache, to keep memory use below the configured limit.

It has been discovered that the effectiveness of the cache-cleaning algorithm used in `named` can be severely diminished by querying the resolver for specific RRsets in a certain order, effectively allowing the configured `max-cache-size` limit to be significantly exceeded.
This issue affects BIND 9 versions 9.11.0 through 9.16.41, 9.18.0 through 9.18.15, 9.19.0 through 9.19.13, 9.11.3-S1 through 9.16.41-S1, and 9.18.11-S1 through 9.18.15-S1.

Project Subscriptions

Vendors Products
Debian Linux Subscribe
Fedoraproject Subscribe
Active Iq Unified Manager Subscribe
H300s Firmware Subscribe
H410c Firmware Subscribe
H410s Firmware Subscribe
H500s Firmware Subscribe
H700s Firmware Subscribe
Enterprise Linux Subscribe
Rhel Aus Subscribe
Rhel E4s Subscribe
Rhel Eus Subscribe
Rhel Tus Subscribe
Advisories
Source ID Title
Debian DLA Debian DLA DLA-3498-1 bind9 security update
Debian DSA Debian DSA DSA-5439-1 bind9 security update
EUVD EUVD EUVD-2023-34279 Every `named` instance configured to run as a recursive resolver maintains a cache database holding the responses to the queries it has recently sent to authoritative servers. The size limit for that cache database can be configured using the `max-cache-size` statement in the configuration file; it defaults to 90% of the total amount of memory available on the host. When the size of the cache reaches 7/8 of the configured limit, a cache-cleaning algorithm starts to remove expired and/or least-recently used RRsets from the cache, to keep memory use below the configured limit. It has been discovered that the effectiveness of the cache-cleaning algorithm used in `named` can be severely diminished by querying the resolver for specific RRsets in a certain order, effectively allowing the configured `max-cache-size` limit to be significantly exceeded. This issue affects BIND 9 versions 9.11.0 through 9.16.41, 9.18.0 through 9.18.15, 9.19.0 through 9.19.13, 9.11.3-S1 through 9.16.41-S1, and 9.18.11-S1 through 9.18.15-S1.
Ubuntu USN Ubuntu USN USN-6183-1 Bind vulnerabilities
Ubuntu USN Ubuntu USN USN-6183-2 Bind vulnerability
Fixes

Solution

Upgrade to the patched release most closely related to your current version of BIND 9: 9.16.42, 9.18.16, 9.19.14, 9.16.42-S1, or 9.18.16-S1.


Workaround

No workarounds known.

History

Fri, 06 Dec 2024 19:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: isc

Published:

Updated: 2025-02-13T16:48:38.124Z

Reserved: 2023-05-22T07:57:41.362Z

Link: CVE-2023-2828

cve-icon Vulnrichment

Updated: 2024-08-02T06:33:05.796Z

cve-icon NVD

Status : Modified

Published: 2023-06-21T17:15:47.703

Modified: 2024-11-21T07:59:22.150

Link: CVE-2023-2828

cve-icon Redhat

Severity : Important

Publid Date: 2023-06-21T00:00:00Z

Links: CVE-2023-2828 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses