BIND 9 Cache Bypass Exploit (named) Allows max-cache-size Exceeded 9.119.19
CVE-2023-2828 Published on June 21, 2023
named's configured cache size limit can be significantly exceeded
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.
Vulnerability Analysis
CVE-2023-2828 is exploitable with network access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity, and a high impact on availability.
Products Associated with CVE-2023-2828
You can be notified by email with stack.watch whenever vulnerabilities like CVE-2023-2828 are published in these products:
Affected Versions
ISC BIND 9:- Version 9.11.0, <= 9.16.41 is affected.
- Version 9.18.0, <= 9.18.15 is affected.
- Version 9.19.0, <= 9.19.13 is affected.
- Version 9.11.3-S1, <= 9.16.41-S1 is affected.
- Version 9.18.11-S1, <= 9.18.15-S1 is affected.
Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.