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-8620

In BIND 9.15.6 -> 9.16.5, 9.17.0 -> 9.17.3, An attacker who can establish a TCP connection with the server and send data on that…

High7.5EPSS 3.9%
Published
Updated
Reserved
Assigned by
isc

Description

In BIND 9.15.6 -> 9.16.5, 9.17.0 -> 9.17.3, An attacker who can establish a TCP connection with the server and send data on that connection can exploit this to trigger the assertion failure, causing the server to exit.

Scores

CVSS scores of CVE-2020-8620, by who scored it
Scored byCVSSScoreVector
iscCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
3.9% · top 9.7% 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: High 7.5.

Weakness

  • In versions of BIND that use the libuv network manager (9.16.x is the only stable branch affected) an incorrectly specified maximum buffer size allows a specially crafted large TCP payload to trigger an assertion failure when it is received. Affects BIND 9.15.6 -> 9.16.5, 9.17.0 -> 9.17.3
  • CWE-617 (opens in a new tab)All about CWE-617 and its CVEs

Affected products

What to do

Solution: Upgrade to the patched release most closely related to your current version of BIND: BIND 9.16.6 BIND 9.17.4

Workaround: No workarounds known.

Exploitation: We are not aware of any active exploits.

References (7)

Sources

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

Badge for a README or a ticket

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

Record last updated .