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

  - In BIND 9.0.0 -> 9.11.29, 9.12.0 -> 9.16.13, and     versions BIND 9.9.3-S1 -> 9.11.29-S1 and 9.16.8-S1 ->     9.16.13-S1 of BIND Supported Preview Edition, as well     as release versions 9.17.0 -> 9.17.11 of the BIND 9.17     development branch, when a vulnerable version of named     receives a query for a record triggering the flaw     described above, the named process will terminate due     to a failed assertion check. The vulnerability affects     all currently maintained BIND 9 branches (9.11, 9.11-S,     9.16, 9.16-S, 9.17) as well as all other versions of     BIND 9.(CVE-2021-25215)

  - In BIND 9.8.5 -> 9.8.8, 9.9.3 -> 9.11.29, 9.12.0 ->     9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and     9.16.8-S1 -> 9.16.13-S1 of BIND 9 Supported Preview     Edition, as well as release versions 9.17.0 -> 9.17.11     of the BIND 9.17 development branch, when a vulnerable     version of named receives a malformed IXFR triggering     the flaw described above, the named process will     terminate due to a failed assertion the next time the     transferred secondary zone is     refreshed.(CVE-2021-25214)

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.

New bind packages are available for Slackware 14.0, 14.1, 14.2, and
-current to fix security issues.

Several vulnerabilities were discovered in BIND, a DNS server implementation.

  - CVE-2021-25214     Greg Kuechle discovered that a malformed incoming IXFR     transfer could trigger an assertion failure in named,     resulting in denial of service.

  - CVE-2021-25215     Siva Kakarla discovered that named could crash when a     DNAME record placed in the ANSWER section during DNAME     chasing turned out to be the final answer to a client     query.

  - CVE-2021-25216     It was discovered that the SPNEGO implementation used by     BIND is prone to a buffer overflow vulnerability. This     update switches to use the SPNEGO implementation from     the Kerberos libraries.

The remote SUSE Linux SLES11 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2021:14714-1 advisory.

  - In BIND 9.8.5 -> 9.8.8, 9.9.3 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and     9.16.8-S1 -> 9.16.13-S1 of BIND 9 Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11     of the BIND 9.17 development branch, when a vulnerable version of named receives a malformed IXFR     triggering the flaw described above, the named process will terminate due to a failed assertion the next     time the transferred secondary zone is refreshed. (CVE-2021-25214)

  - In BIND 9.0.0 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and 9.16.8-S1 ->     9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11 of the BIND     9.17 development branch, when a vulnerable version of named receives a query for a record triggering the     flaw described above, the named process will terminate due to a failed assertion check. The vulnerability     affects all currently maintained BIND 9 branches (9.11, 9.11-S, 9.16, 9.16-S, 9.17) as well as all other     versions of BIND 9. (CVE-2021-25215)

  - In BIND 9.5.0 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.11.3-S1 -> 9.11.29-S1 and 9.16.8-S1 ->     9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.1 of the BIND     9.17 development branch, BIND servers are vulnerable if they are running an affected version and are     configured to use GSS-TSIG features. In a configuration which uses BIND's default settings the vulnerable     code path is not exposed, but a server can be rendered vulnerable by explicitly setting values for the     tkey-gssapi-keytab or tkey-gssapi-credential configuration options. Although the default configuration is     not vulnerable, GSS-TSIG is frequently used in networks where BIND is integrated with Samba, as well as in     mixed-server environments that combine BIND servers with Active Directory domain controllers. For servers     that meet these conditions, the ISC SPNEGO implementation is vulnerable to various attacks, depending on     the CPU architecture for which BIND was built: For named binaries compiled for 64-bit platforms, this flaw     can be used to trigger a buffer over-read, leading to a server crash. For named binaries compiled for     32-bit platforms, this flaw can be used to trigger a server crash due to a buffer overflow and possibly     also to achieve remote code execution. We have determined that standard SPNEGO implementations are     available in the MIT and Heimdal Kerberos libraries, which support a broad range of operating systems,     rendering the ISC implementation unnecessary and obsolete. Therefore, to reduce the attack surface for     BIND users, we will be removing the ISC SPNEGO implementation in the April releases of BIND 9.11 and 9.16     (it had already been dropped from BIND 9.17). We would not normally remove something from a stable ESV     (Extended Support Version) of BIND, but since system libraries can replace the ISC SPNEGO implementation,     we have made an exception in this case for reasons of stability and security. (CVE-2021-25216)

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

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

  - In BIND 9.8.5 -> 9.8.8, 9.9.3 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and     9.16.8-S1 -> 9.16.13-S1 of BIND 9 Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11     of the BIND 9.17 development branch, when a vulnerable version of named receives a malformed IXFR     triggering the flaw described above, the named process will terminate due to a failed assertion the next     time the transferred secondary zone is refreshed. (CVE-2021-25214)

  - In BIND 9.0.0 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and 9.16.8-S1 ->     9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11 of the BIND     9.17 development branch, when a vulnerable version of named receives a query for a record triggering the     flaw described above, the named process will terminate due to a failed assertion check. The vulnerability     affects all currently maintained BIND 9 branches (9.11, 9.11-S, 9.16, 9.16-S, 9.17) as well as all other     versions of BIND 9. (CVE-2021-25215)

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.

According to the versions of the dhcp package installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - In BIND 9.8.5 -> 9.8.8, 9.9.3 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and     9.16.8-S1 -> 9.16.13-S1 of BIND 9 Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11     of the BIND 9.17 development branch, when a vulnerable version of named receives a malformed IXFR     triggering the flaw described above, the named process will terminate due to a failed assertion the next     time the transferred secondary zone is refreshed. (CVE-2021-25214)

  - In BIND 9.0.0 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and 9.16.8-S1 ->     9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11 of the BIND     9.17 development branch, when a vulnerable version of named receives a query for a record triggering the     flaw described above, the named process will terminate due to a failed assertion check. The vulnerability     affects all currently maintained BIND 9 branches (9.11, 9.11-S, 9.16, 9.16-S, 9.17) as well as all other     versions of BIND 9. (CVE-2021-25215)

  - In BIND 9.3.0 -> 9.11.35, 9.12.0 -> 9.16.21, and versions 9.9.3-S1 -> 9.11.35-S1 and 9.16.8-S1 ->     9.16.21-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.18 of the BIND     9.17 development branch, exploitation of broken authoritative servers using a flaw in response processing     can cause degradation in BIND resolver performance. The way the lame cache is currently designed makes it     possible for its internal data structures to grow almost infinitely, which may cause significant delays in     client query processing. (CVE-2021-25219)

  - BIND 9.11.0 -> 9.11.36 9.12.0 -> 9.16.26 9.17.0 -> 9.18.0 BIND Supported Preview Editions: 9.11.4-S1 ->     9.11.36-S1 9.16.8-S1 -> 9.16.26-S1 Versions of BIND 9 earlier than those shown - back to 9.1.0, including     Supported Preview Editions - are also believed to be affected but have not been tested as they are EOL.
    The cache could become poisoned with incorrect records leading to queries being made to the wrong servers,     which might also result in false information being returned to clients. (CVE-2021-25220)

  - In ISC DHCP 4.4.0 -> 4.4.3, ISC DHCP 4.1-ESV-R1 -> 4.1-ESV-R16-P1, when the function     option_code_hash_lookup() is called from add_option(), it increases the option's refcount field. However,     there is not a corresponding call to option_dereference() to decrement the refcount field. The function     add_option() is only used in server responses to lease query packets. Each lease query response calls this     function for several options, so eventually, the reference counters could overflow and cause the server to     abort. (CVE-2022-2928)

  - In ISC DHCP 1.0 -> 4.4.3, ISC DHCP 4.1-ESV-R1 -> 4.1-ESV-R16-P1 a system with access to a DHCP server,     sending DHCP packets crafted to include fqdn labels longer than 63 bytes, could eventually cause the     server to run out of memory. (CVE-2022-2929)

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.

According to the versions of the dhcp package installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - In BIND 9.8.5 -> 9.8.8, 9.9.3 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and     9.16.8-S1 -> 9.16.13-S1 of BIND 9 Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11     of the BIND 9.17 development branch, when a vulnerable version of named receives a malformed IXFR     triggering the flaw described above, the named process will terminate due to a failed assertion the next     time the transferred secondary zone is refreshed. (CVE-2021-25214)

  - In BIND 9.0.0 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and 9.16.8-S1 ->     9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11 of the BIND     9.17 development branch, when a vulnerable version of named receives a query for a record triggering the     flaw described above, the named process will terminate due to a failed assertion check. The vulnerability     affects all currently maintained BIND 9 branches (9.11, 9.11-S, 9.16, 9.16-S, 9.17) as well as all other     versions of BIND 9. (CVE-2021-25215)

  - In BIND 9.3.0 -> 9.11.35, 9.12.0 -> 9.16.21, and versions 9.9.3-S1 -> 9.11.35-S1 and 9.16.8-S1 ->     9.16.21-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.18 of the BIND     9.17 development branch, exploitation of broken authoritative servers using a flaw in response processing     can cause degradation in BIND resolver performance. The way the lame cache is currently designed makes it     possible for its internal data structures to grow almost infinitely, which may cause significant delays in     client query processing. (CVE-2021-25219)

  - BIND 9.11.0 -> 9.11.36 9.12.0 -> 9.16.26 9.17.0 -> 9.18.0 BIND Supported Preview Editions: 9.11.4-S1 ->     9.11.36-S1 9.16.8-S1 -> 9.16.26-S1 Versions of BIND 9 earlier than those shown - back to 9.1.0, including     Supported Preview Editions - are also believed to be affected but have not been tested as they are EOL.
    The cache could become poisoned with incorrect records leading to queries being made to the wrong servers,     which might also result in false information being returned to clients. (CVE-2021-25220)

  - By flooding the target resolver with queries exploiting this flaw an attacker can significantly impair the     resolver's performance, effectively denying legitimate clients access to the DNS resolution service.
    (CVE-2022-2795)

  - In ISC DHCP 4.4.0 -> 4.4.3, ISC DHCP 4.1-ESV-R1 -> 4.1-ESV-R16-P1, when the function     option_code_hash_lookup() is called from add_option(), it increases the option's refcount field. However,     there is not a corresponding call to option_dereference() to decrement the refcount field. The function     add_option() is only used in server responses to lease query packets. Each lease query response calls this     function for several options, so eventually, the reference counters could overflow and cause the server to     abort. (CVE-2022-2928)

  - In ISC DHCP 1.0 -> 4.4.3, ISC DHCP 4.1-ESV-R1 -> 4.1-ESV-R16-P1 a system with access to a DHCP server,     sending DHCP packets crafted to include fqdn labels longer than 63 bytes, could eventually cause the     server to run out of memory. (CVE-2022-2929)

  - By spoofing the target resolver with responses that have a malformed ECDSA signature, an attacker can     trigger a small memory leak. It is possible to gradually erode available memory to the point where named     crashes for lack of resources. (CVE-2022-38177)

  - By spoofing the target resolver with responses that have a malformed EdDSA signature, an attacker can     trigger a small memory leak. It is possible to gradually erode available memory to the point where named     crashes for lack of resources. (CVE-2022-38178)

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.

ID	Name	Product	Family	Published	Updated	Severity
151184	EulerOS Virtualization for ARM 64 3.0.6.0 : bind (EulerOS-SA-2021-2013)	Nessus	Huawei Local Security Checks	6/30/2021	12/12/2023	high
149067	Slackware 14.0 / 14.1 / 14.2 / current : bind (SSA:2021-118-01)	Nessus	Slackware Local Security Checks	4/29/2021	11/9/2021	critical
149229	Debian DSA-4909-1 : bind9 - security update	Nessus	Debian Local Security Checks	5/3/2021	5/14/2021	critical
150646	SUSE SLES11 Security Update : bind (SUSE-SU-2021:14714-1)	Nessus	SuSE Local Security Checks	6/10/2021	11/9/2021	critical
154393	EulerOS 2.0 SP3 : bind (EulerOS-SA-2021-2572)	Nessus	Huawei Local Security Checks	10/25/2021	11/9/2021	high
169869	EulerOS Virtualization 2.10.1 : dhcp (EulerOS-SA-2023-1144)	Nessus	Huawei Local Security Checks	1/11/2023	1/11/2023	medium
176878	EulerOS Virtualization 2.11.1 : dhcp (EulerOS-SA-2023-2035)	Nessus	Huawei Local Security Checks	6/7/2023	6/7/2023	medium
164611	Nutanix AOS : Multiple Vulnerabilities (NXSA-AOS-5.20.3)	Nessus	Misc.	9/1/2022	3/12/2024	critical

Detections

Analytics

Plugins Search

high

critical

critical

critical

high

medium

medium

critical