Improper Access Control Affecting bind-sdb-chroot package, versions <32:9.11.4-9.P2.el7


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.56% (78th 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 Learn

Learn about Improper Access Control vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-BINDSDBCHROOT-4936588
  • published26 Jul 2021
  • disclosed20 Sept 2018

Introduced: 20 Sep 2018

CVE-2018-5741  (opens in a new tab)
CWE-284  (opens in a new tab)

How to fix?

Upgrade RHEL:7 bind-sdb-chroot to version 32:9.11.4-9.P2.el7 or higher.
This issue was patched in RHSA-2019:2057.

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.

To provide fine-grained controls over the ability to use Dynamic DNS (DDNS) to update records in a zone, BIND 9 provides a feature called update-policy. Various rules can be configured to limit the types of updates that can be performed by a client, depending on the key used when sending the update request. Unfortunately, some rule types were not initially documented, and when documentation for them was added to the Administrator Reference Manual (ARM) in change #3112, the language that was added to the ARM at that time incorrectly described the behavior of two rule types, krb5-subdomain and ms-subdomain. This incorrect documentation could mislead operators into believing that policies they had configured were more restrictive than they actually were. This affects BIND versions prior to BIND 9.11.5 and BIND 9.12.3.