Reachable Assertion Affecting bind-sdb-chroot package, versions <32:9.11.4-16.P2.el7_8.6


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
97.28% (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-RHEL7-BINDSDBCHROOT-8011830
  • published17 Sept 2024
  • 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 RHEL:7 bind-sdb-chroot to version 32:9.11.4-16.P2.el7_8.6 or higher.
This issue was patched in RHSA-2020:2344.

NVD Description

Note: Versions mentioned in the description apply only to the upstream bind-sdb-chroot package and not the bind-sdb-chroot package as distributed by RHEL. See How to fix? for RHEL:7 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