Reachable Assertion Affecting bind9 package, versions <1:9.16.3-1


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
97.2% (100th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN11-BIND9-569629
  • published19 May 2020
  • disclosed19 May 2020

Introduced: 19 May 2020

CVE-2020-8617  (opens in a new tab)
CWE-617  (opens in a new tab)

How to fix?

Upgrade Debian:11 bind9 to version 1:9.16.3-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream bind9 package and not the bind9 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

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.

CVSS Scores

version 3.1