named's configured cache size limit can be significantly exceeded
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.5% (FIRST EPSS); higher than 89.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: bind (AlmaLinux:8) 32:9.11.36-8.el8_8.1; bind-chroot (AlmaLinux:8) 32:9.11.36-8.el8_8.1; bind-devel (AlmaLinux:8) 32:9.11.36-8.el8_8.1.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to bind (AlmaLinux:8) 32:9.11.36-8.el8_8.1; bind-chroot (AlmaLinux:8) 32:9.11.36-8.el8_8.1; bind-devel (AlmaLinux:8) 32:9.11.36-8.el8_8.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2023-07642
- ALSA-2023:4099
- ALSA-2023:4100
- ALSA-2023:4102
- DLA-3498-1
- DSA-5439-1
- openSUSE-SU-2024:13015-1
- RHSA-2023:4005
- RHSA-2023:4037
- RHSA-2023:4099
- RHSA-2023:4100
- RHSA-2023:4101
- RHSA-2023:4102
- RHSA-2023:4152
- RHSA-2023:4153
- RHSA-2023:4154
- RHSA-2023:4332
- RLSA-2023:4099
- RLSA-2023:4100
- RLSA-2023:4102
- Published
- Jun 21, 2023
- Updated
- Jun 17, 2026
- EPSS
- 3.5% · 89th percentile
- CWE
- CWE-770
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · isc
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| isc | bind | cpe:2.3:a:isc:bind |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| netapp | active iq unified manager | cpe:2.3:a:netapp:active_iq_unified_manager |
| netapp | h500s firmware | cpe:2.3:o:netapp:h500s_firmware |
| netapp | h500s | cpe:2.3:h:netapp:h500s |
| netapp | h700s firmware | cpe:2.3:o:netapp:h700s_firmware |
| netapp | h700s | cpe:2.3:h:netapp:h700s |
| netapp | h410s firmware | cpe:2.3:o:netapp:h410s_firmware |
| netapp | h410s | cpe:2.3:h:netapp:h410s |
| netapp | h410c firmware | cpe:2.3:o:netapp:h410c_firmware |
| netapp | h410c | cpe:2.3:h:netapp:h410c |
and 2 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- debian debian linux11.0
- debian debian linux12.0
- fedoraproject fedora37
- fedoraproject fedora38
- isc bind9.11.0 and later · up to 9.16.41 inclusive
- isc bind9.11.3 and later · up to 9.16.41 inclusive
- isc bind9.18.0 and later · up to 9.18.15 inclusive
- isc bind9.18.11 and later · up to 9.18.15 inclusive
- isc bind9.19.0 and later · up to 9.19.13 inclusive
- netapp active iq unified managerall versions
- netapp h300s firmwareall versions
- netapp h410c firmwareall versions
- netapp h410s firmwareall versions
- netapp h500s firmwareall versions
- netapp h700s firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (isc). Independent of NVD's CPE analysis and usually ahead of it.
ISC BIND 9
- 9.11.0 and later · up to and including 9.16.41affected
- 9.18.0 and later · up to and including 9.18.15affected
- 9.19.0 and later · up to and including 9.19.13affected
- 9.11.3-S1 and later · up to and including 9.16.41-S1affected
- 9.18.11-S1 and later · up to and including 9.18.15-S1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bind | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-chroot | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-devel | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-export-devel | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-export-libs | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-libs | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-libs-lite | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-license | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-lite-devel | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-pkcs11 | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-pkcs11-devel | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-pkcs11-libs | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-pkcs11-utils | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-sdb | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-sdb-chroot | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind-utils | before 32:9.11.36-8.el8_8.1 | 32:9.11.36-8.el8_8.1 |
| AlmaLinux:8 | bind9.16 | before 32:9.16.23-0.14.el8_8.1.alma | 32:9.16.23-0.14.el8_8.1.alma |
| AlmaLinux:8 | bind9.16-chroot | before 32:9.16.23-0.14.el8_8.1.alma | 32:9.16.23-0.14.el8_8.1.alma |
| AlmaLinux:8 | bind9.16-devel | before 32:9.16.23-0.14.el8_8.1.alma | 32:9.16.23-0.14.el8_8.1.alma |
| AlmaLinux:8 | bind9.16-dnssec-utils | before 32:9.16.23-0.14.el8_8.1.alma | 32:9.16.23-0.14.el8_8.1.alma |
| AlmaLinux:8 | bind9.16-doc | before 32:9.16.23-0.14.el8_8.1.alma | 32:9.16.23-0.14.el8_8.1.alma |
| AlmaLinux:8 | bind9.16-libs | before 32:9.16.23-0.14.el8_8.1.alma | 32:9.16.23-0.14.el8_8.1.alma |
| AlmaLinux:8 | bind9.16-license | before 32:9.16.23-0.14.el8_8.1.alma | 32:9.16.23-0.14.el8_8.1.alma |
| AlmaLinux:8 | bind9.16-utils | before 32:9.16.23-0.14.el8_8.1.alma | 32:9.16.23-0.14.el8_8.1.alma |
+96
Same product
isc: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-5477named in ISC BIND 9.x before 9.9.7-P2 and 9.10.x before 9.10.2-P3 allows remote attackers to cause a denial of service (REQUIRE assertion faKEV90Now
- CVE-2020-8617A logic error in code which checks TSIG validity can be used to trigger an assertion failure in tsig.c60This week
- CVE-2016-2776buffer.c in named in ISC BIND 9 before 9.9.9-P3, 9.10.x before 9.10.4-P3, and 9.11.x before 9.11.0rc3 does not properly construct responses,60This week
Published before and after this one in the same product
- ← EarlierCVE-2022-3736Jan 26, 2023 · named configured to answer from stale cache may terminate unexpectedly while processing RRSIG queries45Plan
- ← EarlierCVE-2022-3924Jan 26, 2023 · named configured to answer from stale cache may terminate unexpectedly at recursive-clients soft quota35Monitor
- Later →CVE-2023-2829Jun 21, 2023 · Malformed NSEC records can cause named to terminate unexpectedly when synth-from-dnssec is enabled30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:bind | 32:9.16.23-11.el9_2.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:bind-chroot | 32:9.16.23-11.el9_2.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:bind-devel | 32:9.16.23-11.el9_2.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:bind-dnssec-doc | 32:9.16.23-11.el9_2.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:bind-dnssec-utils | 32:9.16.23-11.el9_2.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:bind-doc | 32:9.16.23-11.el9_2.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:bind-libs | 32:9.16.23-11.el9_2.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:bind-license | 32:9.16.23-11.el9_2.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:bind-utils | 32:9.16.23-11.el9_2.1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:bind9.16 | 32:9.16.23-0.14.el8_8.1.alma · AlmaLinux:8 | Package registry (OSV) |
| almalinux:bind9.16-chroot | 32:9.16.23-0.14.el8_8.1.alma · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3-bind | 32:9.16.23-11.el9_2.1 · AlmaLinux:9 | Package registry (OSV) |
| debian:bind9 | 1:9.18.16-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:bind | 9.16.42-150400.5.27.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:bind | 32:9.16.23-1.el9_0.2 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| red hat:bind-chroot | 32:9.16.23-1.el9_0.2 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| red hat:bind-debuginfo | 32:9.16.23-1.el9_0.2 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| red hat:bind-debugsource | 32:9.16.23-1.el9_0.2 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| red hat:bind-dnssec-doc | 32:9.16.23-1.el9_0.2 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| red hat:bind-dnssec-utils | 32:9.16.23-1.el9_0.2 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| red hat:bind-dnssec-utils-debuginfo | 32:9.16.23-1.el9_0.2 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| red hat:bind-libs | 32:9.16.23-1.el9_0.2 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| red hat:bind-libs-debuginfo | 32:9.16.23-1.el9_0.2 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| red hat:bind-license | 32:9.16.23-1.el9_0.2 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| red hat:bind-utils | 32:9.16.23-1.el9_0.2 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| red hat:bind-utils-debuginfo | 32:9.16.23-1.el9_0.2 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| rocky linux:bind | 2:9.16.23-11.el9_2.1 · Rocky Linux:9 | Package registry (OSV) |
| rocky linux:bind9.16 | 2:9.16.23-0.14.el8_8.1 · Rocky Linux:8 | Package registry (OSV) |
| suse:bind | 9.16.42-150400.5.27.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Shoham DaninoReichman University, Anat Bremler-Barr
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0499 · Sep 7, 2023(Multicluster Engine Güvenlik Zafiyeti)
- TR-23-0437 · Aug 2, 2023(Mozilla Firefox Güvenlik Güncellemesi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- kb.isc.org/docs/cve-2023-2828
- lists.debian.org/debian-lts-announce/2023/07/msg00021.html
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SEFCEVCTYEMKTWA7V7EYPI5YQQ4JWDLI/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/U3K6AJK7RRSR53HRF5GGKPA6PDUDWOD2/
- security.netapp.com/advisory/ntap-20230703-0010/
- www.debian.org/security/2023/dsa-5439
Vendor advisories and official records. Exploit/PoC links are deliberately left out.