CVE Vulnerabilities

CVE-2020-8617

Reachable Assertion

Published: May 19, 2020 | Modified: Nov 21, 2024
CVSS 3.x
5.9
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
4.3 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

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.

Weakness

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

Affected Software

NameVendorStart VersionEnd Version
BindIsc9.0.0 (including)9.11.18 (including)
BindIsc9.12.0 (including)9.12.4 (including)
BindIsc9.13.0 (including)9.13.7 (including)
BindIsc9.14.0 (including)9.14.11 (including)
BindIsc9.15.0 (including)9.15.6 (including)
BindIsc9.16.0 (including)9.16.2 (including)
BindIsc9.17.0 (including)9.17.1 (including)
BindIsc9.12.4-p1 (including)9.12.4-p1 (including)
BindIsc9.12.4-p2 (including)9.12.4-p2 (including)
Red Hat Enterprise Linux 6RedHatbind-32:9.8.2-0.68.rc1.el6_10.7*
Red Hat Enterprise Linux 6.5 Advanced Update SupportRedHatbind-32:9.8.2-0.23.rc1.el6_5.9*
Red Hat Enterprise Linux 6.6 Advanced Update SupportRedHatbind-32:9.8.2-0.30.rc1.el6_6.11*
Red Hat Enterprise Linux 7RedHatbind-32:9.11.4-16.P2.el7_8.6*
Red Hat Enterprise Linux 7.2 Advanced Update SupportRedHatbind-32:9.9.4-29.el7_2.9*
Red Hat Enterprise Linux 7.3 Advanced Update SupportRedHatbind-32:9.9.4-50.el7_3.4*
Red Hat Enterprise Linux 7.3 Telco Extended Update SupportRedHatbind-32:9.9.4-50.el7_3.4*
Red Hat Enterprise Linux 7.3 Update Services for SAP SolutionsRedHatbind-32:9.9.4-50.el7_3.4*
Red Hat Enterprise Linux 7.4 Advanced Update SupportRedHatbind-32:9.9.4-51.el7_4.4*
Red Hat Enterprise Linux 7.4 Telco Extended Update SupportRedHatbind-32:9.9.4-51.el7_4.4*
Red Hat Enterprise Linux 7.4 Update Services for SAP SolutionsRedHatbind-32:9.9.4-51.el7_4.4*
Red Hat Enterprise Linux 7.6 Extended Update SupportRedHatbind-32:9.9.4-74.el7_6.4*
Red Hat Enterprise Linux 7.7 Extended Update SupportRedHatbind-32:9.11.4-9.P2.el7_7.1*
Red Hat Enterprise Linux 8RedHatbind-32:9.11.13-5.el8_2*
Red Hat Enterprise Linux 8RedHatbind-32:9.11.13-5.el8_2*
Red Hat Enterprise Linux 8.0 Update Services for SAP SolutionsRedHatbind-32:9.11.4-19.P2.el8_0*
Red Hat Enterprise Linux 8.1 Extended Update SupportRedHatbind-32:9.11.4-26.P2.el8_1.3*
Bind9Ubuntubionic*
Bind9Ubuntudevel*
Bind9Ubuntueoan*
Bind9Ubuntuesm-infra-legacy/trusty*
Bind9Ubuntuesm-infra/bionic*
Bind9Ubuntuesm-infra/focal*
Bind9Ubuntuesm-infra/xenial*
Bind9Ubuntufocal*
Bind9Ubuntutrusty*
Bind9Ubuntutrusty/esm*
Bind9Ubuntuxenial*

Extended Description

While assertion is good for catching logic errors and reducing the chances of reaching more serious vulnerability conditions, it can still lead to a denial of service. For example, if a server handles multiple simultaneous connections, and an assert() occurs in one single connection that causes all other connections to be dropped, this is a reachable assertion that leads to a denial of service.

Potential Mitigations

References