The remote MiracleLinux 8 host has packages installed that are affected by a vulnerability as referenced in the AXSA:2024-7684:04 advisory.

    * A vulnerability was found in Unbound due to incorrect default permissions, allowing any process outside     the unbound group to modify the unbound runtime configuration. The default combination of the control-     use-cert: no option with either explicit or implicit use of an IP address in the control-interface     option could allow improper access. If a process can connect over localhost to port 8953, it can alter the     configuration of unbound.service. This flaw allows an unprivileged local process to manipulate a running     instance, potentially altering forwarders, allowing them to track all queries forwarded by the local     resolver, and, in some cases, disrupting resolving altogether.
    To mitigate the vulnerability, a new file /etc/unbound/conf.d/remote-control.conf has been added and     included in the main unbound configuration file, unbound.conf. The file contains two directives that     should limit access to unbound.conf:
    control-interface: /run/unbound/control     control-use-cert: yes     For details about these directives, run man unbound.conf.
    Updating to the version of unbound provided by this advisory should, in most cases, address the     vulnerability. To verify that your configuration is not vulnerable, use the unbound-control status | grep     control command. If the output contains control(ssl) or control(namedpipe), your configuration is not     vulnerable. If the command output returns only control, the configuration is vulnerable because it does     not enforce access only to the unbound group members. To fix your configuration, add the line include:
    /etc/unbound/conf.d/remote-control.conf to the end of the file /etc/unbound/unbound.conf. If you use a     custom /etc/unbound/conf.d/remote-control.conf file, add the new directives to this file.
    (CVE-2024-1488)

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 Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:2587 advisory.

    The unbound packages provide a validating, recursive, and caching DNS or     DNSSEC resolver.

    Security Fix(es):

    * bind9: KeyTrap - Extreme CPU consumption in DNSSEC validator     (CVE-2023-50387)

    * bind9: Preparing an NSEC3 closest encloser proof can exhaust CPU     resources (CVE-2023-50868)

    * A vulnerability was found in Unbound due to incorrect default     permissions, allowing any process outside the unbound group to modify the unbound runtime configuration.
    The default combination of the control-use-cert: no option with either explicit or implicit use of an IP     address in the control-interface option could allow improper access. If a process can connect over     localhost to port 8953, it can alter the configuration of unbound.service. This flaw allows an     unprivileged local process to manipulate a running instance, potentially altering forwarders, allowing     them to track all queries forwarded by the local resolver, and, in some cases, disrupting resolving     altogether.

    To mitigate the vulnerability, a new file /etc/unbound/conf.d/remote-control.conf has been added and     included in the main unbound configuration file, unbound.conf. The file contains two directives that     should limit access to unbound.conf:

        control-interface: /run/unbound/control         control-use-cert: yes

    For details about these directives, run man unbound.conf.

    Updating to the version of unbound provided by this advisory should, in     most cases, address the vulnerability. To verify that your configuration is not vulnerable, use the     unbound-control status | grep control command. If the output contains control(ssl) or     control(namedpipe), your configuration is not vulnerable. If the command output returns only control,     the configuration is vulnerable because it does not enforce access only to the unbound group members. To     fix your configuration, add the line include: /etc/unbound/conf.d/remote-control.conf to the end of the     file /etc/unbound/unbound.conf. If you use a custom /etc/unbound/conf.d/remote-control.conf file, add     the new directives to     this file. (CVE-2024-1488)

    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.

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.

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

    The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped)     allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC     responses in a random subdomain attack, aka the 'NSEC3' issue. The RFC 5155 specification implies that an     algorithm must perform thousands of iterations of a hash function in certain situations.(CVE-2023-50868)

    Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote     attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the     'KeyTrap' issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the     protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG     records.(CVE-2023-50387)

    A vulnerability was found in Unbound due to incorrect default permissions, allowing any process outside     the unbound group to modify the unbound runtime configuration. If a process can connect over localhost to     port 8953, it can alter the configuration of unbound.service. This flaw allows an unprivileged attacker to     manipulate a running instance, potentially altering forwarders, allowing them to track all queries     forwarded by the local resolver, and, in some cases, disrupting resolving altogether.(CVE-2024-1488)

Tenable has extracted the preceding description block directly from the EulerOS unbound 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 unbound packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

    The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped)     allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC     responses in a random subdomain attack, aka the 'NSEC3' issue. The RFC 5155 specification implies that an     algorithm must perform thousands of iterations of a hash function in certain situations.(CVE-2023-50868)

    Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote     attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the     'KeyTrap' issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the     protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG     records.(CVE-2023-50387)

    A vulnerability was found in Unbound due to incorrect default permissions, allowing any process outside     the unbound group to modify the unbound runtime configuration. If a process can connect over localhost to     port 8953, it can alter the configuration of unbound.service. This flaw allows an unprivileged attacker to     manipulate a running instance, potentially altering forwarders, allowing them to track all queries     forwarded by the local resolver, and, in some cases, disrupting resolving altogether.(CVE-2024-1488)

Tenable has extracted the preceding description block directly from the EulerOS Virtualization unbound 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 unbound packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote     attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the     'KeyTrap' issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the     protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG     records.(CVE-2023-50387)

    The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped)     allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC     responses in a random subdomain attack, aka the 'NSEC3' issue. The RFC 5155 specification implies that an     algorithm must perform thousands of iterations of a hash function in certain situations.(CVE-2023-50868)

    A vulnerability was found in Unbound due to incorrect default permissions, allowing any process outside     the unbound group to modify the unbound runtime configuration. If a process can connect over localhost to     port 8953, it can alter the configuration of unbound.service. This flaw allows an unprivileged attacker to     manipulate a running instance, potentially altering forwarders, allowing them to track all queries     forwarded by the local resolver, and, in some cases, disrupting resolving altogether.(CVE-2024-1488)

Tenable has extracted the preceding description block directly from the EulerOS unbound 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	名称	产品	系列	发布时间	最近更新时间	严重程度
293592	MiracleLinux 8 : unbound-1.16.2-5.el8_9.6 (AXSA:2024-7684:04)	Nessus	Miracle Linux Local Security Checks	2026/1/20	2026/1/20	high
194819	RHEL 8 : unbound (RHSA-2024:2587)	Nessus	Red Hat Local Security Checks	2024/4/30	2025/12/24	high
201147	EulerOS 2.0 SP12 : unbound (EulerOS-SA-2024-1877)	Nessus	Huawei Local Security Checks	2024/6/28	2025/12/24	high
202650	EulerOS Virtualization 2.10.1 : unbound (EulerOS-SA-2024-2012)	Nessus	Huawei Local Security Checks	2024/7/18	2025/12/24	high
202659	EulerOS Virtualization 2.10.0 : unbound (EulerOS-SA-2024-1994)	Nessus	Huawei Local Security Checks	2024/7/18	2025/12/24	high
207623	EulerOS 2.0 SP8 : unbound (EulerOS-SA-2024-2494)	Nessus	Huawei Local Security Checks	2024/9/24	2025/12/24	high

检测

插件搜索

high

high

high

high

high

high