ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2023-2828

Every 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.

Published Jun 21, 2023 · catalog updated Oct 24, 2026 · Every instance configured to

Open the advisory

Exploitation likelihood is not on this record for CVE-2023-2828. A missing EPSS score is not a low risk. Compare Every instance configured to with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Every instance configured to).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Not in the current FIRST EPSS dataset
Remediation
Version ranges on file
Affected products
cpe debian/debian linux · cpe isc/bind

Every 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 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 can be severely diminished by querying the resolver for specific RRsets in a certain order, effectively allowing the configured 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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe debian/debian linux10.0
  • cpe debian/debian linux11.0
  • cpe debian/debian linux12.0
  • cpe isc/bind>= 9.11.0, <= 9.16.41
  • cpe isc/bind>= 9.11.3, <= 9.16.41
  • cpe isc/bind>= 9.18.0, <= 9.18.15
  • cpe isc/bind>= 9.18.11, <= 9.18.15
  • cpe isc/bind>= 9.19.0, <= 9.19.13

How to fix CVE-2023-2828

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for CVE-2023-2828. A missing EPSS score is not a low risk. Compare Every instance configured to with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with debian/debian linux 10.0; debian/debian linux 11.0; debian/debian linux 12.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-770: Allocation of Resources Without Limits or Throttling. EPSS is absent from the current FIRST dataset. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 21, 2023 · NIST NVD

    Detected

    Every 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 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

  2. Oct 24, 2026 · NIST NVD

    Updated

    Every 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 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

Sources

  • CVE.orgVulnerability recordCVE-2023-2828

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2023-2828

    Every 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 statement in the con

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 24, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.