Homepage
About Snyk

Reachable Assertion Affecting bind9 package, versions <1:9.9.5.dfsg-9+deb8u19

0.0
medium

Snyk CVSS

    Attack Complexity High
    Availability High

    Threat Intelligence

    EPSS 97.25% (100th percentile)
Expand this section
NVD
5.9 medium
Expand this section
SUSE
7.5 high
Expand this section
Red Hat
7.5 high

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 ID SNYK-DEBIAN8-BIND9-569633
  • published 19 May 2020
  • disclosed 19 May 2020
Report a new vulnerability Found a mistake?

Introduced: 19 May 2020

CVE-2020-8617 Open this link in a new tab
CWE-617 Open this link in a new tab

How to fix?

Upgrade Debian:8 bind9 to version 1:9.9.5.dfsg-9+deb8u19 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:8 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.

References