https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-38178 ISC BIND is vulnerable to a denial of service, caused by a memory leak in the DNSSEC verification code for the EdDSA algorithm. By spoofing the target resolver with responses that have a malformed EdDSA signature, a remote attacker could exploit this vulnerability to cause named to crash. ISC BIND is vulnerable to a denial of service, caused by an error when stale cache and stale answers are enabled, option stale-answer-client-timeout is set to 0 and there is a stale CNAME in the cache for an incoming query. By sending a specially-crafted request, a remote attacker could exploit this vulnerability to cause named to crash. ISC BIND is vulnerable to a denial of service, caused by a small memory leak in the DNSSEC verification code for the ECDSA algorithm. By spoofing the target resolver with responses that have a malformed ECDSA signature, a remote attacker could exploit this vulnerability to cause named to crash. ISC BIND is vulnerable to a denial of service, caused by a flaw in resolver code. By flooding the target resolver with queries, a remote attacker could exploit this vulnerability to severely degrade the resolver's performance, effectively denying legitimate clients access to the DNS resolution service.

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2023:3002 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: processing large delegations may severely degrade resolver performance (CVE-2022-2795)

    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.8 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 this issue but has instead relied only on the application's self-reported version number.

The remote MiracleLinux 8 host has packages installed that are affected by a vulnerability as referenced in the AXSA:2023-5855:05 advisory.

    * bind: processing large delegations may severely degrade resolver performance (CVE-2022-2795)

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

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

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

    - CVE-2022-2795: Fixed potential performance degredation due to missing database lookup limits when     processing large delegations (bsc#1203614).
      - CVE-2022-38177: Fixed a memory leak that could be externally triggered in the DNSSEC verification code     for the ECDSA algorithm (bsc#1203619).

Tenable has extracted the preceding description block directly from the SUSE 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 SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:3767-1 advisory.

    Update to release 9.16.33:

    - CVE-2022-2795: Fixed potential performance degredation due to missing database lookup limits when     processing large delegations (bsc#1203614).
    - CVE-2022-3080: Fixed assertion failure when there was a stale CNAME in the cache for the incoming query     and the stale-answer-client-timeout option is set to 0 (bsc#1203618).
    - CVE-2022-38177: Fixed a memory leak that could be externally triggered in the DNSSEC verification code     for the ECDSA algorithm (bsc#1203619).
    - CVE-2022-38178: Fixed memory leaks that could be externally triggered in the DNSSEC verification code     for the EdDSA algorithm (bsc#1203620).

    - Add systemd drop-in directory for named service (bsc#1201689).
    - Add modified createNamedConfInclude script and README-bind.chrootenv (bsc#1203250).

    - Feature Changes:
      - Response Rate Limiting (RRL) code now treats all QNAMEs that are       subject to wildcard processing within a given zone as the same       name, to prevent circumventing the limits enforced by RRL.

      - Zones using dnssec-policy now require dynamic DNS or       inline-signing to be configured explicitly.

      - A backward-compatible approach was implemented for encoding       internationalized domain names (IDN) in dig and converting the       domain to IDNA2008 form; if that fails,       BIND tries an IDNA2003 conversion.

      - The DNSSEC algorithms RSASHA1 and NSEC3RSASHA1 are now automatically       disabled on systems where they are disallowed by the security policy.
      Primary zones using those algorithms need to be migrated to new algorithms       prior to running on these systems, as graceful migration to different DNSSEC       algorithms is not possible when RSASHA1 is disallowed by the operating system.

      - Log messages related to fetch limiting have been improved to provide       more complete information. Specifically, the final counts of allowed       and spilled fetches are now logged before the counter object is destroyed.

      - Non-dynamic zones that inherit dnssec-policy from the view or options       blocks were not marked as inline-signed and therefore never scheduled       to be re-signed. This has been fixed.

      - The old max-zone-ttl zone option was meant to be superseded by       the max-zone-ttl option in dnssec-policy; however, the latter option       was not fully effective. This has been corrected: zones no longer load       if they contain TTLs greater than the limit configured in dnssec-policy.
      For zones with both the old max-zone-ttl option and dnssec-policy       configured, the old option is ignored, and a warning is generated.

      - rndc dumpdb -expired was fixed to include expired RRsets,       even if stale-cache-enable is set to no and the cache-cleaning time       window has passed. (jsc#SLE-24600)

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

Note that Nessus has not tested for these issues 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 :

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

  - By sending specific queries to the resolver, an attacker can cause named to crash. (CVE-2022-3080)

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

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

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

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

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 version of AHV installed on the remote host is prior to 20220304.10055. It is, therefore, affected by multiple vulnerabilities as referenced in the NXSA-AHV-20220304.10055 advisory.

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

  - PAC parsing in MIT Kerberos 5 (aka krb5) before 1.19.4 and 1.20.x before 1.20.1 has integer overflows that     may lead to remote code execution (in KDC, kadmind, or a GSS or Kerberos application server) on 32-bit     platforms (which have a resultant heap-based buffer overflow), and cause a denial of service on other     platforms. This occurs in krb5_pac_parse in lib/krb5/krb/pac.c. Heimdal before 7.7.1 has a similar bug.
    (CVE-2022-42898)

  - In Sudo before 1.9.12p2, the sudoedit (aka -e) feature mishandles extra arguments passed in the user-     provided environment variables (SUDO_EDITOR, VISUAL, and EDITOR), allowing a local attacker to append     arbitrary entries to the list of files to process. This can lead to privilege escalation. Affected     versions are 1.8.0 through 1.9.12.p1. The problem exists because a user-specified editor may contain a
    -- argument that defeats a protection mechanism, e.g., an EDITOR='vim -- /path/to/extra/file' value.
    (CVE-2023-22809)

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

  - multipath-tools 0.7.0 through 0.9.x before 0.9.2 allows local users to obtain root access, as exploited     alone or in conjunction with CVE-2022-41973. Local users able to write to UNIX domain sockets can bypass     access controls and manipulate the multipath setup. This can lead to local privilege escalation to root.
    This occurs because an attacker can repeat a keyword, which is mishandled because arithmetic ADD is used     instead of bitwise OR. (CVE-2022-41974)

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 Tencent Linux installed on the remote TencentOS Server 3 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2023:0071 advisory.

    Package updates are available for TencentOS Server 3 that fix the following vulnerabilities:

      CVE-2022-3094:
      A flaw was found in Bind, where sending a flood of dynamic DNS updates may cause named to allocate large     amounts of memory. This issue may cause named to exit due to a lack of free memory, resulting in a denial     of service (DoS).
      CVE-2022-3094:
      A flaw was found in Bind, where sending a flood of dynamic DNS updates may cause named to allocate large     amounts of memory. This issue may cause named to exit due to a lack of free memory, resulting in a denial     of service (DoS).
      CVE-2022-3736:
      A flaw was found in Bind, where a resolver crash is possible. When stale cache and stale answers are     enabled, the option stale-answer-client-timeout is set to a positive integer, and the resolver receives an     RRSIG query.
      CVE-2022-3924:
      A flaw was found in Bind. When resolver receives many queries requiring recursion, there will be a     corresponding increase in the number of clients waiting for recursion to complete. This may, under certain     conditions, lead to an assertion failure and a denial of service.
      CVE-2022-2795:
      A flaw was found in bind. When flooding the target resolver with special queries, an attacker can     significantly impair the resolver's performance, effectively denying legitimate clients access to the DNS     resolution service.
      CVE-2022-3080:
      A flaw was found in the Bind package, where the resolver can crash when stale cache and stale answers     are enabled, option stale-answer-client-timeout is set to 0 and there is a stale CNAME in the cache for an     incoming query. By sending specific queries to the resolver, an attacker can cause named to crash.
      CVE-2022-38177:
      A flaw was found in the Bind package. By spoofing the target resolver with responses that have a     malformed ECDSA signature, an attacker can trigger a small memory leak, resulting in crashing the program.
      CVE-2022-38178:
      A flaw was found in the Bind package, where the DNSSEC verification code for the EdDSA algorithm leaks     memory when there is a signature length mismatch. By spoofing the target resolver with responses that have     a malformed EdDSA signature, an attacker can trigger a small memory leak, resulting in crashing the     program.
      CVE-2021-25220:
      A cache poisoning vulnerability was found in BIND when using forwarders. Bogus NS records supplied by     the forwarders may be cached and used by name if it needs to recurse for any reason. This issue causes it     to obtain and pass on potentially incorrect answers. This flaw allows a remote high privileged attacker to     manipulate cache results with incorrect records, leading to queries made to the wrong servers, possibly     resulting in false information received on the client's end.

Tenable has extracted the preceding description block directly from the Tencent 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.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
169316	AIX 7.1 TL 5 : bind (IJ44422)	Nessus	AIX Local Security Checks	2022/12/27	2023/4/20	high
175853	RHEL 8 : bind (RHSA-2023:3002)	Nessus	Red Hat Local Security Checks	2023/5/16	2024/11/7	medium
292021	MiracleLinux 8 : bind-9.11.36-8.el8 (AXSA:2023-5855:05)	Nessus	Miracle Linux Local Security Checks	2026/1/20	2026/1/20	medium
165692	SUSE SLES12: bind / bind-chrootenv / bind-doc / bind-libs / bind-libs-32bit / etc (SUSE-SU-2022:3500-1)	Nessus	SuSE Local Security Checks	2022/10/5	2026/6/25	medium
166581	SUSE SLED15 / SLES15 / openSUSE 15 : Recommended update for bind (SUSE-SU-2022:3767-1)	Nessus	SuSE Local Security Checks	2022/10/27	2026/6/26	medium
169547	EulerOS 2.0 SP11 : bind (EulerOS-SA-2023-1002)	Nessus	Huawei Local Security Checks	2023/1/5	2023/1/26	high
169668	EulerOS 2.0 SP9 : bind (EulerOS-SA-2023-1093)	Nessus	Huawei Local Security Checks	2023/1/6	2023/1/6	high
183341	Nutanix AHV : Multiple Vulnerabilities (NXSA-AHV-20220304.10055)	Nessus	Misc.	2023/10/18	2025/2/17	medium
238587	TencentOS Server 3: bind9.16 (TSSA-2023:0071)	Nessus	Tencent Local Security Checks	2025/6/16	2025/11/20	medium

检测

插件搜索

high

medium

medium

medium

medium

high

high

medium

medium