'managed-keys' is a feature which allows a BIND resolver to automatically maintain the keys used by trust anchors which operators configure for use in DNSSEC validation. Due to an error in the managed-keys feature it is possible for a BIND server which uses managed-keys to exit due to an assertion failure if, during key rollover, a trust anchor's keys are replaced with keys which use an unsupported algorithm. Versions affected: BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.5-P1, 9.12.0 -> 9.12.3-P1, and versions 9.9.3-S1 -> 9.11.5-S3 of BIND 9 Supported Preview Edition. Versions 9.13.0 -> 9.13.6 of the 9.13 development branch are also affected. Versions prior to BIND 9.9.0 have not been evaluated for vulnerability to CVE-2018-5745. (CVE-2018-5745)

Impact

BIG-IP

An arbitrary attacker may exploit this vulnerability to cause a denial of service (DoS) on the named service.

BIG-IQ, F5 iWorkflow, and Enterprise Manager

These F5 products are not vulnerablein the default, standard, and recommended configurations. This vulnerability is exposed on these products when a custom configurationis applied to the named service.

Traffix SDC

There is no impact for thisF5 product; it isnot affected by this vulnerability.

This update for bind fixes the following issues :

Security issues fixed :

CVE-2019-6465: Fixed an issue where controls for zone transfers may not be properly applied to Dynamically Loadable Zones (bsc#1126069).

CVE-2018-5745: Fixed a denial of service vulnerability if a trust anchor rolls over to an unsupported key algorithm when using managed-keys (bsc#1126068).

CVE-2018-5743: Fixed a denial of service vulnerability which could be caused by to many simultaneous TCP connections (bsc#1133185).

CVE-2018-5740: Fixed a denial of service vulnerability in the 'deny-answer-aliases' feature (bsc#1104129).

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

According to the versions of the bind packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - An assertion failure was found in the way bind     implemented the 'managed keys' feature. An attacker     could use this flaw to cause the named daemon to crash.
    This flaw is very difficult for an attacker to trigger     because it requires an operator to have BIND configured     to use a trust anchor managed by the     attacker.(CVE-2018-5745)

  - It was found that the controls for zone transfer were     not properly applied to Dynamically Loadable Zones     (DLZs). An attacker acting as a DNS client could use     this flaw to request and receive a zone transfer of a     DLZ even when not permitted to do so by the     'allow-transfer' ACL.(CVE-2019-6465)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2019:3552 advisory.

    The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols.
    BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing     with DNS); and tools for verifying that the DNS server is operating correctly.

    Security Fix(es):

    * bind: An assertion failure if a trust anchor rolls over to an unsupported key algorithm when using     managed-keys (CVE-2018-5745)

    * bind: Controls for zone transfers may not be properly applied to DLZs if the zones are writable     (CVE-2019-6465)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 8.1 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of bind installed on the remote host is prior to 9.11.4-9.P2. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2020-1441 advisory.

    managed-keys is a feature which allows a BIND resolver to automatically maintain the keys used by trust     anchors which operators configure for use in DNSSEC validation. Due to an error in the managed-keys     feature it is possible for a BIND server which uses managed-keys to exit due to an assertion failure if,     during key rollover, a trust anchor's keys are replaced with keys which use an unsupported algorithm.
    Versions affected: BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.5-P1, 9.12.0 -> 9.12.3-P1, and versions     9.9.3-S1 -> 9.11.5-S3 of BIND 9 Supported Preview Edition. Versions 9.13.0 -> 9.13.6 of the 9.13     development branch are also affected. Versions prior to BIND 9.9.0 have not been evaluated for     vulnerability toCVE-2018-5745. (CVE-2018-5745)

    With pipelining enabled each incoming query on a TCP connection requires a similar resource allocation to     a query received via UDP or via TCP without pipelining enabled. A client using a TCP-pipelined connection     to a server could consume more resources than the server has been provisioned to handle. When a TCP     connection with a large number of pipelined queries is closed, the load on the server releasing these     multiple resources can cause it to become unresponsive, even for queries that can be answered     authoritatively or from cache. (This is most likely to be perceived as an intermittent server problem).
    (CVE-2019-6477)

    Controls for zone transfers may not be properly applied to Dynamically Loadable Zones (DLZs) if the zones     are writable Versions affected: BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.5-P2, 9.12.0 -> 9.12.3-P2, and     versions 9.9.3-S1 -> 9.11.5-S3 of BIND 9 Supported Preview Edition. Versions 9.13.0 -> 9.13.6 of the 9.13     development branch are also affected. Versions prior to BIND 9.9.0 have not been evaluated for     vulnerability toCVE-2019-6465. (CVE-2019-6465)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote NewStart CGSL host, running version CORE 5.05 / MAIN 5.05, has bind packages installed that are affected by multiple vulnerabilities:

  - managed-keys is a feature which allows a BIND resolver to automatically maintain the keys used by trust     anchors which operators configure for use in DNSSEC validation. Due to an error in the managed-keys     feature it is possible for a BIND server which uses managed-keys to exit due to an assertion failure if,     during key rollover, a trust anchor's keys are replaced with keys which use an unsupported algorithm.
    Versions affected: BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.5-P1, 9.12.0 -> 9.12.3-P1, and versions     9.9.3-S1 -> 9.11.5-S3 of BIND 9 Supported Preview Edition. Versions 9.13.0 -> 9.13.6 of the 9.13     development branch are also affected. Versions prior to BIND 9.9.0 have not been evaluated for     vulnerability to CVE-2018-5745. (CVE-2018-5745)

  - Controls for zone transfers may not be properly applied to Dynamically Loadable Zones (DLZs) if the zones     are writable Versions affected: BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.5-P2, 9.12.0 -> 9.12.3-P2, and     versions 9.9.3-S1 -> 9.11.5-S3 of BIND 9 Supported Preview Edition. Versions 9.13.0 -> 9.13.6 of the 9.13     development branch are also affected. Versions prior to BIND 9.9.0 have not been evaluated for     vulnerability to CVE-2019-6465. (CVE-2019-6465)

  - With pipelining enabled each incoming query on a TCP connection requires a similar resource allocation to     a query received via UDP or via TCP without pipelining enabled. A client using a TCP-pipelined connection     to a server could consume more resources than the server has been provisioned to handle. When a TCP     connection with a large number of pipelined queries is closed, the load on the server releasing these     multiple resources can cause it to become unresponsive, even for queries that can be answered     authoritatively or from cache. (This is most likely to be perceived as an intermittent server problem).
    (CVE-2019-6477)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	名前	製品	ファミリー	公開日	更新日	深刻度
122554	F5 Networks BIG-IP : BIND vulnerability (K25244852)	Nessus	F5 Networks Local Security Checks	2019/3/4	2026/10/21	medium
125703	SUSE SLED15 / SLES15 Security Update : bind (SUSE-SU-2019:1407-1)	Nessus	SuSE Local Security Checks	2019/6/4	2021/1/13	medium
128191	EulerOS 2.0 SP8 : bind (EulerOS-SA-2019-1822)	Nessus	Huawei Local Security Checks	2019/8/27	2024/5/1	medium
130551	RHEL 8 : bind (RHSA-2019:3552)	Nessus	Red Hat Local Security Checks	2019/11/6	2024/11/7	medium
138043	Amazon Linux 2 : bind (ALAS-2020-1441)	Nessus	Amazon Linux Local Security Checks	2020/7/2	2024/12/11	medium
144003	NewStart CGSL CORE 5.05 / MAIN 5.05 : bind Multiple Vulnerabilities (NS-SA-2020-0095)	Nessus	NewStart CGSL Local Security Checks	2020/12/9	2020/12/10	medium

検出

プラグインの検索

medium

medium

medium

medium

medium

medium