CVE-2020-8617

published 19 May 2020 · updated 16 Sep 2024

A logic error in code which checks TSIG validity can be used to trigger an assertion failure in tsig.c

9.5CriticalCVSS 7.5EPSS 93%1 public exploits

A public exploit exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 93%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
ISCBIND99.0.0 - >9.11.18 9.12.0 - >9.12.4-P2 9.14.0 - >9.14.11 9.16.0 - >9.16.2 and releases 9.17.0 - >9.17.1 of the 9.17 experimental development branch. All releases in the obsolete 9.13 and 9.15 development branches. All releases of BIND Supported Preview Edition from 9.9.3-S1 - >9.11.18-S1

Exploit evidence

1 public sources

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in ISC, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2020-8617 severity on Zeptric[![CVE-2020-8617](https://zeptric.io/badge/cve/CVE-2020-8617.svg)](https://zeptric.io/cve/CVE-2020-8617)