CVE-2023-6516
No exploitation reported by the sources we read.
- Published2024-02-13
- WeaknessCWE-770 · CWE-789
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2024-02-1314:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-6516?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-6516?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · CISA-ADP| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 9.16 | ≥ 9.16.0, ≤ 9.16.45 | no fix published | NVD · CISA-ADP |
| 9.16 | = 9.16.8 | no fix published | NVD |
| 9.16 | = 9.16.11 | no fix published | NVD |
| 9.16 | = 9.16.12 | no fix published | NVD |
| 9.16 | = 9.16.13 | no fix published | NVD |
| 9.16 | = 9.16.14 | no fix published | NVD |
| 9.16 | = 9.16.21 | no fix published | NVD |
| 9.16 | = 9.16.32 | no fix published | NVD |
| 9.16 | = 9.16.36 | no fix published | NVD |
| 9.16 | = 9.16.43 | no fix published | NVD |
| 9.16 | = 9.16.45 | no fix published | NVD |
| 9.16 | ≥ 9.16.8-s1, ≤ 9.16.45-s1 | no fix published | CISA-ADP |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| — | all versions | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- kb.isc.orgVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2024-02-13
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2023-6516?
Is CVE-2023-6516 actively exploited?
What is the CVSS score for CVE-2023-6516?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.