CVE-2020-8617

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

Published May 19, 2020 CVSS 3.1 · 7.5 High EPSS 93.3% KEV · Not listed
Description
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.

Remediation

Vendor Solution

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


Vendor Workaround

None known.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-2227-1 bind9 security update
Debian DSA Debian DSA DSA-4689-1 bind9 security update
Ubuntu USN Ubuntu USN USN-4365-1 Bind vulnerabilities
Ubuntu USN Ubuntu USN USN-4365-2 Bind vulnerabilities
History

No history.