CVE-2023-2828
HIGHEPSS 89th pctlDescription
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.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Elevated risk: more likely to be exploited than 89% of all known CVEs.
References
Related Vulnerabilities
Other CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-50387 | High | 7.5 | 100% | - | Fix |
| CVE-2019-11478 | Medium | 5.3 | 95% | - | Fix |
| CVE-2019-11479 | High | 7.5 | 92% | - | Fix |
| CVE-2024-27316 | High | 7.5 | 91% | - | Fix |
| CVE-2022-30522 | High | 7.5 | 90% | - | Fix |
| CVE-2019-9515 | High | 7.5 | 87% | - | Fix |
Common questions
How do I fix CVE-2023-2828?
Published advisories record a fix for 128 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2023-2828 being actively exploited?
Not that we know of. CVE-2023-2828 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 3.8% is the estimated probability that it will be exploited in the next 30 days. That is higher than 89% of all scored CVEs.
How severe is CVE-2023-2828?
CVE-2023-2828 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2023-2828 affect?
Published advisories record a fix for bind (Amazon), bind-chroot (Amazon), bind-debuginfo (Amazon), bind-debugsource (Amazon), and 124 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2023-2828
Markdown
[](https://tridentstack.com/cve/CVE-2023-2828)HTML
<a href="https://tridentstack.com/cve/CVE-2023-2828"><img src="https://tridentstack.com/cve/badge/CVE-2023-2828.svg" alt="CVE-2023-2828"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-17.