CVE-2023-6516

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2024-02-13. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
64th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 13, 2024

Last Modified

November 21, 2024

References (10)

Vendor Advisories for CVE-2023-6516(8)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntudnsutils (1:9.16.48-0ubuntu0.20.04.1) @ focal2026-05-24ubuntu
redhatbind-dyndb-ldap-0:11.9-9.el9_42024-04-30redhat
redhatbind-dyndb-ldap-0:11.9-7.el9_0.12024-04-15redhat
redhatbind-dyndb-ldap-0:11.9-8.el9_2.22024-04-15redhat
redhatbind9.16-32:9.16.23-0.16.el8_9.22024-04-11redhat
redhatbind-dyndb-ldap-0:11.9-8.el9_3.32024-04-11redhat
redhatbind9.16-32:9.16.23-0.14.el8_8.42024-04-02redhat
redhatbind9.16-32:9.16.23-0.7.el8_6.52024-04-02redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(13 across 13 ecosystems)
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.16.0 up to 9.16.48-r0: fixed in 9.16.48-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.16.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.16.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.16.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.16.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.16.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.16.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.16.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.16.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.16.15-1 ... 1:9.16.44-1~deb11u1 (11 versions)
  • every version up to 1:9.16.48-1: fixed in 1:9.16.48-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.17.19-1: fixed in 1:9.17.19-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.17.19-1: fixed in 1:9.17.19-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.17.19-1: fixed in 1:9.17.19-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 179 total refreshes for this CVE.

  1. 2026-10-09 20:05 UTCEPSS rescore
  2. 2026-10-08 17:06 UTCEPSS rescore
  3. 2026-10-07 23:46 UTCEPSS rescore
  4. 2026-10-06 15:15 UTCEPSS rescore
  5. 2026-10-05 17:41 UTCEPSS rescore
  6. 2026-10-04 23:20 UTCEPSS rescore
  7. 2026-10-03 14:23 UTCEPSS rescore
  8. 2026-10-01 19:48 UTCEPSS rescore
  9. 2026-10-01 19:48 UTCEPSS rescore
  10. 2026-09-30 16:39 UTCEG score recompute
  11. 2026-09-30 15:01 UTCEPSS rescore
  12. 2026-09-30 15:01 UTCEPSS rescore
  13. 2026-09-29 15:17 UTCEPSS rescore
  14. 2026-09-28 13:49 UTCEPSS rescore
  15. 2026-09-26 00:22 UTCEPSS rescore
  16. 2026-09-24 14:01 UTCEPSS rescore
  17. 2026-09-24 14:01 UTCEPSS rescore
  18. 2026-09-23 13:46 UTCEPSS rescore
  19. 2026-09-22 08:45 UTCOSV refresh
  20. 2026-09-20 20:14 UTCEPSS rescore
  21. 2026-09-20 20:14 UTCEPSS rescore
  22. 2026-09-18 19:26 UTCEPSS rescore
  23. 2026-09-16 14:06 UTCEPSS rescore
  24. 2026-09-16 05:11 UTCEPSS rescore
  25. 2026-09-16 05:11 UTCEPSS rescore
Show 75 more
  1. 2026-09-15 03:08 UTCEPSS rescore
  2. 2026-09-13 16:45 UTCEPSS rescore
  3. 2026-09-12 14:58 UTCEPSS rescore
  4. 2026-09-11 14:51 UTCEPSS rescore
  5. 2026-09-11 09:34 UTCEPSS rescore
  6. 2026-09-08 21:58 UTCEPSS rescore
  7. 2026-09-06 13:46 UTCEPSS rescore
  8. 2026-09-05 15:26 UTCEPSS rescore
  9. 2026-09-04 13:58 UTCEPSS rescore
  10. 2026-09-04 05:04 UTCEPSS rescore
  11. 2026-09-03 05:59 UTCOSV refresh
  12. 2026-09-02 14:10 UTCEPSS rescore
  13. 2026-09-01 13:52 UTCEPSS rescore
  14. 2026-09-01 04:36 UTCEPSS rescore
  15. 2026-08-30 19:15 UTCEPSS rescore
  16. 2026-08-30 01:20 UTCEPSS rescore
  17. 2026-08-28 21:39 UTCEPSS rescore
  18. 2026-08-27 14:23 UTCEPSS rescore
  19. 2026-08-26 14:44 UTCEPSS rescore
  20. 2026-08-25 13:47 UTCEPSS rescore
  21. 2026-08-23 00:17 UTCEPSS rescore
  22. 2026-08-23 00:17 UTCEPSS rescore
  23. 2026-08-21 23:47 UTCEPSS rescore
  24. 2026-08-20 22:53 UTCEPSS rescore
  25. 2026-08-19 17:02 UTCEPSS rescore
  26. 2026-08-18 13:46 UTCEPSS rescore
  27. 2026-08-16 19:26 UTCOSV refresh
  28. 2026-08-16 14:54 UTCEPSS rescore
  29. 2026-08-16 02:12 UTCEPSS rescore
  30. 2026-08-15 01:28 UTCEPSS rescore
  31. 2026-08-13 21:58 UTCEPSS rescore
  32. 2026-08-12 13:49 UTCEPSS rescore
  33. 2026-08-11 13:40 UTCEPSS rescore
  34. 2026-08-10 23:58 UTCEPSS rescore
  35. 2026-08-09 13:44 UTCEPSS rescore
  36. 2026-08-08 16:35 UTCEPSS rescore
  37. 2026-08-07 16:25 UTCEPSS rescore
  38. 2026-08-06 13:45 UTCEPSS rescore
  39. 2026-08-05 19:15 UTCEPSS rescore
  40. 2026-08-05 19:15 UTCEPSS rescore
  41. 2026-08-04 10:36 UTCEPSS rescore
  42. 2026-08-03 10:34 UTCEPSS rescore
  43. 2026-08-02 02:25 UTCEPSS rescore
  44. 2026-08-02 02:25 UTCEPSS rescore
  45. 2026-08-01 13:06 UTCOSV refresh
  46. 2026-08-01 04:14 UTCEPSS rescore
  47. 2026-07-30 16:26 UTCEPSS rescore
  48. 2026-07-30 01:29 UTCEPSS rescore
  49. 2026-07-28 15:34 UTCEPSS rescore
  50. 2026-07-28 15:34 UTCEPSS rescore
  51. 2026-07-26 14:53 UTCEPSS rescore
  52. 2026-07-25 14:16 UTCEPSS rescore
  53. 2026-07-24 14:16 UTCEPSS rescore
  54. 2026-07-23 14:16 UTCEPSS rescore
  55. 2026-07-23 02:30 UTCEG score recompute
  56. 2026-07-22 23:17 UTCEG score recompute
  57. 2026-07-22 14:07 UTCEPSS rescore
  58. 2026-07-22 14:07 UTCEPSS rescore
  59. 2026-07-21 15:23 UTCEPSS rescore
  60. 2026-07-20 17:06 UTCEPSS rescore
  61. 2026-07-19 14:30 UTCEPSS rescore
  62. 2026-07-19 14:29 UTCEPSS rescore
  63. 2026-07-19 02:27 UTCEPSS rescore
  64. 2026-07-19 02:27 UTCEPSS rescore
  65. 2026-07-18 10:03 UTCEPSS rescore
  66. 2026-07-18 10:03 UTCEPSS rescore
  67. 2026-07-16 17:01 UTCEPSS rescore
  68. 2026-07-15 16:56 UTCEPSS rescore
  69. 2026-07-15 01:59 UTCEPSS rescore
  70. 2026-07-15 01:59 UTCEPSS rescore
  71. 2026-07-14 19:55 UTCOSV refresh
  72. 2026-07-13 22:28 UTCEPSS rescore
  73. 2026-07-13 22:28 UTCEPSS rescore
  74. 2026-07-13 06:11 UTCEPSS rescore
  75. 2026-07-12 05:45 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-6516?
CVE-2023-6516 is a high vulnerability published on February 13, 2024. 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…
When was CVE-2023-6516 disclosed?
CVE-2023-6516 was first published on February 13, 2024, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-6516 actively exploited?
CVE-2023-6516 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-6516?
CVE-2023-6516 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2023-6516?
A fix for CVE-2023-6516 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-6516 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-6516

Explore →

Is Your Infrastructure Affected by CVE-2023-6516?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs