ISC BIND 9.16.21 S1 Supported Preview Edition

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:isc:bind:9.16.21:s1:*:*:supported_preview:*:*:*

part: a version: 9.16.21 update: s1

VendorIsc (4a2f2b37-98b6-5702-822d-72afcd17d050)
ProductBind (ea404969-e27c-5a4f-ab6f-da9eff8fdf08)
Edition*
Language*
Software editionsupported_preview
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:github/isc-projects/bind9 purl2cpe 2026-06-01 10:15:10.890523
pkg:gitlab/isc-projects/bind9 purl2cpe 2026-06-01 10:15:10.890524

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-6516 vulnerable 2026-06-08 06:19:47.533004 Specific recursive query patterns may lead to an out-of-memory condition
HIGH (7.5)
To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to clean up the database. It uses several methods, including some that are asynchronous: a small chunk of memory pointing to the cache element that can be cleaned up is first allocated and then queued for later processing. It was discovered that if the resolver is continuously processing query patterns triggering this type of cache-database maintenance, `named` may not be able to handle the cleanup events in a timely manner. This in turn enables the list of queued cleanup events to grow infinitely large over time, allowing the configured `max-cache-size` limit to be significantly exceeded. This issue affects BIND 9 versions 9.16.0 through 9.16.45 and 9.16.8-S1 through 9.16.45-S1.
Published: 2024-02-13T14:05:28.933Z
Updated: 2025-02-13T17:26:26.170Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-5680 vulnerable 2026-06-08 06:19:44.477480 Cleaning an ECS-enabled cache may cause excessive CPU load
MEDIUM (5.3)
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.
Published: 2024-02-13T14:05:19.783Z
Updated: 2025-03-17T15:04:41.734Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-5679 vulnerable 2026-06-08 06:19:44.452787 Enabling both DNS64 and serve-stale may cause an assertion failure during recursive resolution
HIGH (7.5)
A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure during recursive resolution, when both of these features are enabled. This issue affects BIND 9 versions 9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.12-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.
Published: 2024-02-13T14:05:06.688Z
Updated: 2025-03-28T23:51:12.042Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-5517 vulnerable 2026-06-08 06:19:43.927487 Querying RFC 1918 reverse zones may cause an assertion failure when "nxdomain-redirect" is enabled
HIGH (7.5)
A flaw in query-handling code can cause `named` to exit prematurely with an assertion failure when: - `nxdomain-redirect <domain>;` is configured, and - the resolver receives a PTR query for an RFC 1918 address that would normally result in an authoritative NXDOMAIN response. This issue affects BIND 9 versions 9.12.0 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.8-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.
Published: 2024-02-13T14:04:54.389Z
Updated: 2025-02-13T17:25:39.556Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-4408 vulnerable 2026-06-08 06:16:12.310769 Parsing large DNS messages may cause excessive CPU load
HIGH (7.5)
The DNS message parsing code in `named` includes a section whose computational complexity is overly high. It does not cause problems for typical DNS traffic, but crafted queries and responses may cause excessive CPU load on the affected `named` instance by exploiting this flaw. This issue affects both authoritative servers and recursive resolvers. This issue affects BIND 9 versions 9.0.0 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.9.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.
Published: 2024-02-13T14:04:17.519Z
Updated: 2025-03-14T16:16:25.564Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-3341 vulnerable 2026-06-08 06:09:39.292303 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-3924 vulnerable 2026-06-08 05:48:22.639303 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-3736 vulnerable 2026-06-08 05:48:21.779912 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-3094 vulnerable 2026-06-08 05:47:19.425336 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-3080 vulnerable 2026-06-08 05:47:19.158326 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-38178 vulnerable 2026-06-08 05:47:15.997940 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-38177 vulnerable 2026-06-08 05:47:15.991366 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-2795 vulnerable 2026-06-08 05:43:36.514055 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-25219 vulnerable 2026-06-08 05:30:40.338204 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.