Cleaning an ECS-enabled cache may cause excessive CPU load

Description

If a resolver cache has a very large number of ECS records stored for the same name, the process of cleaning the cache database node for this name can significantly impair query performance. This issue affects BIND 9 versions 9.11.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.

Scores

EPSS (exploitation in 30 days)

0.62% · top 50% of all CVEs (7 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.3.

Weakness

• CWE-noinfo Not enough information

Affected products

• ISC · BIND 9

  • affected 9.11.3-S1 – ≤ 9.11.37-S1
  • affected 9.16.8-S1 – ≤ 9.16.45-S1
  • affected 9.18.11-S1 – ≤ 9.18.21-S1

What to do

Solution: Upgrade to the patched release most closely related to your current version of BIND 9: 9.16.48-S1 or 9.18.24-S1.

Workaround: There is no workaround for this issue other than disabling the ECS feature entirely.

Exploitation: We are not aware of any active exploits.

References (2)

• CVE-2023-5680 (opens in a new tab)vendor-advisoryx_transferred
• https://security.netapp.com/advisory/ntap-20240503-0005/ (opens in a new tab)x_transferred

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2023-5680](https://trackcve.app/badge/CVE-2023-5680.svg)](https://trackcve.app/cve/CVE-2023-5680)

Record last updated 17 Mar 2025, 15:04 UTC.