Approved changes feed: RSS · Atom

cpe:2.3:a:isc:bind:9.12.4:p2:*:*:*:*:*:*

part: a version: 9.12.4 update: p2

VendorIsc (4a2f2b37-98b6-5702-822d-72afcd17d050)
ProductBind (ea404969-e27c-5a4f-ab6f-da9eff8fdf08)
Edition*
Language*
Software edition*
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.890321
pkg:gitlab/isc-projects/bind9 purl2cpe 2026-06-01 10:15:10.890322

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2020-8617 vulnerable 2026-06-03 14:43:09.862466 A logic error in code which checks TSIG validity can be used to trigger an assertion failure in tsig.c
HIGH (7.5)
Using a specially-crafted message, an attacker may potentially cause a BIND server to reach an inconsistent state if the attacker knows (or successfully guesses) the name of a TSIG key used by the server. Since BIND, by default, configures a local session key even on servers whose configuration does not otherwise make use of it, almost all current BIND servers are vulnerable. In releases of BIND dating from March 2018 and after, an assertion check in tsig.c detects this inconsistent state and deliberately exits. Prior to the introduction of the check the server would continue operating in an inconsistent state, with potentially harmful results.
Published: 2020-05-19T14:05:16.241Z
Updated: 2024-09-16T20:26:32.566Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-8616 vulnerable 2026-06-03 14:43:09.853104 BIND does not sufficiently limit the number of fetches performed when processing referrals
HIGH (8.6)
A malicious actor who intentionally exploits this lack of effective limitation on the number of fetches performed when processing referrals can, through the use of specially crafted referrals, cause a recursing server to issue a very large number of fetches in an attempt to process the referral. This has at least two potential effects: The performance of the recursing server can potentially be degraded by the additional work required to perform these fetches, and The attacker can exploit this behavior to use the recursing server as a reflector in a reflection attack with a high amplification factor.
Published: 2020-05-19T14:05:15.798Z
Updated: 2024-09-16T23:55:28.601Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2019-6477 vulnerable 2026-06-03 14:40:39.385918 TCP-pipelined queries can bypass tcp-clients limit
HIGH (7.5)
With pipelining enabled each incoming query on a TCP connection requires a similar resource allocation to a query received via UDP or via TCP without pipelining enabled. A client using a TCP-pipelined connection to a server could consume more resources than the server has been provisioned to handle. When a TCP connection with a large number of pipelined queries is closed, the load on the server releasing these multiple resources can cause it to become unresponsive, even for queries that can be answered authoritatively or from cache. (This is most likely to be perceived as an intermittent server problem).
Published: 2019-11-26T16:11:16.500Z
Updated: 2024-09-16T16:47:45.899Z
Reference links
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.