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.21, 9.12.0 -> 9.16.5, 9.17.0 ->     9.17.3, also affects 9.9.3-S1 -> 9.11.21-S1 of the BIND     9 Supported Preview Edition, An attacker on the network     path for a TSIG-signed request, or operating the server     receiving the TSIG-signed request, could send a     truncated response to that request, triggering an     assertion failure, causing the server to exit.
    Alternately, an off-path attacker would have to     correctly guess when a TSIG-signed request was sent,     along with other characteristics of the packet and     message, and spoof a truncated response to trigger an     assertion failure, causing the server to     exit.(CVE-2020-8622)

  - In BIND 9.10.0 -> 9.11.21, 9.12.0 -> 9.16.5, 9.17.0 ->     9.17.3, also affects 9.10.5-S1 -> 9.11.21-S1 of the     BIND 9 Supported Preview Edition, An attacker that can     reach a vulnerable system with a specially crafted     query packet can trigger a crash. To be vulnerable, the     system must: * be running BIND that was built with     '--enable-native-pkcs11' * be signing one or more zones     with an RSA key * be able to receive queries from a     possible attacker(CVE-2020-8623)

  - 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.

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

  - CVE-2020-8619     It was discovered that an asterisk character in an empty     non terminal can cause an assertion failure, resulting     in denial of service.

  - CVE-2020-8622     Dave Feldman, Jeff Warren, and Joel Cunningham reported     that a truncated TSIG response can lead to an assertion     failure, resulting in denial of service.

  - CVE-2020-8623     Lyu Chiy reported that a flaw in the native PKCS#11 code     can lead to a remotely triggerable assertion failure,     resulting in denial of service.

  - CVE-2020-8624     Joop Boonen reported that update-policy rules of type     'subdomain' are enforced incorrectly, allowing updates     to all parts of the zone along with the intended     subdomain.

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.0.0 -> 9.11.21, 9.12.0 -> 9.16.5, 9.17.0 ->     9.17.3, also affects 9.9.3-S1 -> 9.11.21-S1 of the BIND     9 Supported Preview Edition, An attacker on the network     path for a TSIG-signed request, or operating the server     receiving the TSIG-signed request, could send a     truncated response to that request, triggering an     assertion failure, causing the server to exit.
    Alternately, an off-path attacker would have to     correctly guess when a TSIG-signed request was sent,     along with other characteristics of the packet and     message, and spoof a truncated response to trigger an     assertion failure, causing the server to     exit.(CVE-2020-8622)

  - A malicious actor who intentionally exploits this lack     of effective limitation on the number of fetches     performed when processing referrals can, through the     use of specially crafted referrals, cause a recursing     server to issue a very large number of fetches in an     attempt to process the referral. This has at least two     potential effects: The performance of the recursing     server can potentially be degraded by the additional     work required to perform these fetches, and The     attacker can exploit this behavior to use the recursing     server as a reflector in a reflection attack with a     high amplification factor.(CVE-2020-8616)

  - 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.(CVE-2020-8617)

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 NewStart CGSL host, running version MAIN 4.06, has bind packages installed that are affected by multiple vulnerabilities:

  - 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. (CVE-2020-8617)

  - A malicious actor who intentionally exploits this lack of effective limitation on the number of fetches     performed when processing referrals can, through the use of specially crafted referrals, cause a recursing     server to issue a very large number of fetches in an attempt to process the referral. This has at least     two potential effects: The performance of the recursing server can potentially be degraded by the     additional work required to perform these fetches, and The attacker can exploit this behavior to use the     recursing server as a reflector in a reflection attack with a high amplification factor. (CVE-2020-8616)

  - In BIND 9.0.0 -> 9.11.21, 9.12.0 -> 9.16.5, 9.17.0 -> 9.17.3, also affects 9.9.3-S1 -> 9.11.21-S1 of the     BIND 9 Supported Preview Edition, An attacker on the network path for a TSIG-signed request, or operating     the server receiving the TSIG-signed request, could send a truncated response to that request, triggering     an assertion failure, causing the server to exit. Alternately, an off-path attacker would have to     correctly guess when a TSIG-signed request was sent, along with other characteristics of the packet and     message, and spoof a truncated response to trigger an assertion failure, causing the server to exit.
    (CVE-2020-8622)

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

The version of AOS installed on the remote host is prior to 5.19.1. It is, therefore, affected by multiple vulnerabilities as referenced in the NXSA-AOS-5.19.1 advisory.

  - In Network Security Services (NSS) before 3.46, several cryptographic primitives had missing length     checks. In cases where the application calling the library did not perform a sanity check on the inputs it     could result in a crash due to a buffer overflow. (CVE-2019-17006)

  - Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3. (CVE-2019-5482)

  - In all versions of cpio before 2.13 does not properly validate input files when generating TAR archives.
    When cpio is used to create TAR archives from paths an attacker can write to, the resulting archive may     contain files with permissions the attacker did not have or in paths he did not have access to. Extracting     those archives from a high-privilege user without carefully reviewing them may lead to the compromise of     the system. (CVE-2019-14866)

  - If an HTTP/2 client connecting to Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37 or 8.5.0 to     8.5.57 exceeded the agreed maximum number of concurrent streams for a connection (in violation of the     HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP     headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This     could lead to users seeing responses for unexpected resources. (CVE-2020-13943)

  - Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported     versions that are affected are 5.6.45 and prior, 5.7.27 and prior and 8.0.17 and prior. Easily exploitable     vulnerability allows low privileged attacker with network access via multiple protocols to compromise     MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang     or frequently repeatable crash (complete DOS) of MySQL Server. (CVE-2019-2974)

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

ID	Name	Product	Family	Published	Updated	Severity
151313	EulerOS Virtualization for ARM 64 3.0.2.0 : bind (EulerOS-SA-2021-2092)	Nessus	Huawei Local Security Checks	7/2/2021	12/11/2023	high
139930	Debian DSA-4752-1 : bind9 - security update	Nessus	Debian Local Security Checks	8/28/2020	6/3/2021	medium
140830	EulerOS 2.0 SP3 : bind (EulerOS-SA-2020-2063)	Nessus	Huawei Local Security Checks	9/28/2020	2/19/2024	high
147339	NewStart CGSL MAIN 4.06 : bind Multiple Vulnerabilities (NS-SA-2021-0003)	Nessus	NewStart CGSL Local Security Checks	3/10/2021	1/11/2024	high
164584	Nutanix AOS : Multiple Vulnerabilities (NXSA-AOS-5.19.1)	Nessus	Misc.	9/1/2022	7/22/2025	critical

Detections

Analytics

Plugins Search

high

medium

high

high

critical