CoreCVE
Back

HIGH

named's configured cache size limit can be significantly exceeded

Published Jun 21, 2023

Description

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.

Affected products

Remediation

Vendor 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.

Metrics

Weaknesses (1)

CWE-770

Allocation of Resources Without Limits

References (11)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner isc
Published Jun 21, 2023
Updated Feb 13, 2025
Reserved May 22, 2023
Link CVE-2023-2828
CISA Vulnrichment
Updated Dec 6, 2024
NVD
Status Modified
Modified Jun 17, 2026
Link CVE-2023-2828
Red Hat
Severity Important
Public date Jun 21, 2023
Links CVE-2023-2828 - Bugzilla