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.

Affected products

Almalinux, Bind 9, Bind Server, Centos, Ibm Aix, Linuxmint, Red Hat, Rocky Linux

Isc Bind

≤ 9.16.45, 9.16.8, 9.16.11, 9.16.12, 9.16.13, 9.16.14, 9.16.21, 9.16.32, 9.16.36, 9.16.43

Fix

Available

CVSS 3.1

7.5 HIGH

EPSS

1.1% (63th percentile)

Weakness

CWE-789, CWE-770

NVD status

Modified

Published

2024-02-13

No exploit for CVE-2023-6516 has been indexed yet. Our index is built from live traffic and upstream syncs, so this page can only say what it knows — not that no exploit exists.