Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2020-8619

A buffer boundary check assertion in rdataset.c can fail incorrectly during zone transfer

Medium4.9EPSS 2.1%
Published
Updated
Reserved
Assigned by
isc

Description

In ISC BIND9 versions BIND 9.11.14 -> 9.11.19, BIND 9.14.9 -> 9.14.12, BIND 9.16.0 -> 9.16.3, BIND Supported Preview Edition 9.11.14-S1 -> 9.11.19-S1: Unless a nameserver is providing authoritative service for one or more zones and at least one zone contains an empty non-terminal entry containing an asterisk ("*") character, this defect cannot be encountered. A would-be attacker who is allowed to change zone content could theoretically introduce such a record in order to exploit this condition to cause denial of service, though we consider the use of this vector unlikely because any such attack would require a significant privilege level and be easily traceable.

Scores

CVSS scores of CVE-2020-8619, by who scored it
Scored byCVSSScoreVector
iscCNA (assigner)3.1Medium4.9CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium4.9CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
2.1% · top 18% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.9.

Weakness

  • The asterisk character ("*") is allowed in DNS zone files, where it is most commonly present as a wildcard at a terminal node of the Domain Name System graph. However, the RFCs do not require and BIND does not enforce that an asterisk character be present only at a terminal node. A problem can occur when an asterisk is present in an empty non-terminal location within the DNS graph. If such a node exists, after a series of queries, named can reach an inconsistent state that results in the failure of an assertion check in rbtdb.c, followed by the program exiting due to the assertion failure. Versions affected: BIND 9.11.14 -> 9.11.19, BIND 9.14.9 -> 9.14.12, BIND 9.16.0 -> 9.16.3. Also, versions 9.11.14-S1 -> 9.11.19-S1 of BIND Supported Preview Edition
  • CWE-404 (opens in a new tab)All about CWE-404 and its CVEs

Affected products

  • ISC · BIND9

    • affected 9.11.14 through versions before 9.11.20
    • affected 9.16.0 through versions before 9.16.4
    • affected 9.11.14-S1 through versions before 9.11.20-S1
    • affected 9.14.9 through versions 9.14.12

What to do

Solution: Upgrade to the patched release most closely related to your current version of BIND: BIND 9.11.20 BIND 9.16.4 BIND Supported Preview Edition is a special feature preview branch of BIND provided to eligible ISC support customers. BIND 9.11.20-S1

Workaround: None

References (8)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2020-8619 badge
[![CVE-2020-8619](https://trackcve.app/badge/CVE-2020-8619.svg)](https://trackcve.app/cve/CVE-2020-8619)

Record last updated .