The remote Fedora 39 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2024-b0f9656a76 advisory.

    Update to latest upstream.
    Fixes CVE-2023-50387 and CVE-2023-50868


Tenable has extracted the preceding description block directly from the Fedora 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 Fedora 38 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2024-c36c448396 advisory.

    # Security Fixes

    -    Validating DNS messages containing a lot of DNSSEC signatures could cause excessive CPU load, leading     to a denial-of-service condition. This has been fixed.
    ([CVE-2023-50387](https://kb.isc.org/docs/cve-2023-50387))

        ISC would like to thank Elias Heftrig, Haya Schulmann, Niklas Vogel, and Michael Waidner from the     German National Research Center for Applied Cybersecurity ATHENE for bringing this vulnerability to our     attention. [GL #4424]

    -    Parsing DNS messages with many different names could cause excessive CPU load. This has been fixed.
    ([CVE-2023-4408](https://kb.isc.org/docs/cve-2023-4408))

        ISC would like to thank Shoham Danino from Reichman University, Anat Bremler-Barr from Tel-Aviv     University, Yehuda Afek from Tel-Aviv University, and Yuval Shavitt from Tel-Aviv University for bringing     this vulnerability to our attention. [GL #4234]

    -    Specific queries could cause named to crash with an assertion failure when nxdomain-redirect was     enabled. This has been fixed. ([CVE-2023-5517](https://kb.isc.org/docs/cve-2023-5517)) [GL #4281]

    -    A bad interaction between DNS64 and serve-stale could cause named to crash with an assertion failure,     when both of these features were enabled. This has been fixed.
    ([CVE-2023-5679](https://kb.isc.org/docs/cve-2023-5679)) [GL #4334]

    ## Related blog post

    - [BIND 9 Security Release and Multi-Vendor Vulnerability Handling, CVE-2023-50387 and     CVE-2023-50868](https://www.isc.org/blogs/2024-bind-security-release/)

Tenable has extracted the preceding description block directly from the Fedora 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 Ubuntu 20.04 LTS / 22.04 LTS / 23.10 host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-6665-1 advisory.

    Elias Heftrig, Haya Schulmann, Niklas Vogel, and Michael Waidner discovered that Unbound incorrectly     handled validating DNSSEC messages. A remote attacker could possibly use this issue to cause Unbound to     consume resources, leading to a denial of service. (CVE-2023-50387)

    It was discovered that Unbound incorrectly handled preparing an NSEC3 closest encloser proof. A remote     attacker could possibly use this issue to cause Unbound to consume resources, leading to a denial of     service. (CVE-2023-50868)

Tenable has extracted the preceding description block directly from the Ubuntu 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 AlmaLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2024:0965 advisory.

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

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

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2024-550 advisory.

    The DNS message parsing code in `named` includes a section whose computational complexity is overly high.
    It does not cause problems for typical DNS traffic, but crafted queries and responses may cause excessive     CPU load on the affected `named` instance by exploiting this flaw. This issue affects both authoritative     servers and recursive resolvers.This issue affects BIND 9 versions 9.0.0 through 9.16.45, 9.18.0 through     9.18.21, 9.19.0 through 9.19.19, 9.9.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.45-S1, and 9.18.11-S1     through 9.18.21-S1. (CVE-2023-4408)

    Certain DNSSEC aspects of the DNS protocol (in RFC 4035 and related RFCs) allow remote attackers to cause     a denial of service (CPU consumption) via one or more DNSSEC responses when there is a zone with many     DNSKEY and RRSIG records, aka the KeyTrap issue. 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 flaw in query-handling code can cause `named` to exit prematurely with an assertion failure when:

    - `nxdomain-redirect <domain>;` is configured, and- the resolver receives a PTR query for an RFC 1918     address that would normally result in an authoritative NXDOMAIN response.This issue affects BIND 9     versions 9.12.0 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.8-S1 through     9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1. (CVE-2023-5517)

    A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure     during recursive resolution, when both of these features are enabled.This issue affects BIND 9 versions     9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.12-S1 through 9.16.45-S1,     and 9.18.11-S1 through 9.18.21-S1. (CVE-2023-5679)

    To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to     clean up the database. It uses several methods, including some that are asynchronous: a small chunk of     memory pointing to the cache element that can be cleaned up is first allocated and then queued for later     processing. It was discovered that if the resolver is continuously processing query patterns triggering     this type of cache-database maintenance, `named` may not be able to handle the cleanup events in a timely     manner. This in turn enables the list of queued cleanup events to grow infinitely large over time,     allowing the configured `max-cache-size` limit to be significantly exceeded.This issue affects BIND 9     versions 9.16.0 through 9.16.45 and 9.16.8-S1 through 9.16.45-S1. (CVE-2023-6516)

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

    The dnsmasq packages contain Dnsmasq, a lightweight DNS (Domain Name Server) forwarder and DHCP (Dynamic     Host Configuration Protocol) server.

    Security Fix(es):

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

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

    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.

The version of F5 Networks BIG-IP installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the K000139092 advisory.

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

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 :

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

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 Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-6723-1 advisory.

    Elias Heftrig, Haya Schulmann, Niklas Vogel, and Michael Waidner discovered that Bind icorrectly handled     validating DNSSEC messages. A remote attacker could possibly use this issue to cause Bind to consume     resources, leading to a denial of service. (CVE-2023-50387)

    It was discovered that Bind incorrectly handled preparing an NSEC3 closest encloser proof. A remote     attacker could possibly use this issue to cause Bind to consume resources, leading to a denial of service.
    (CVE-2023-50868)

Tenable has extracted the preceding description block directly from the Ubuntu 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 Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:1789 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: Preparing an NSEC3 closest encloser proof can exhaust CPU resources (CVE-2023-50868)

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

    * bind: Specific recursive query patterns may lead to an out-of-memory condition (CVE-2023-6516)

    * bind: Enabling both DNS64 and serve-stale may cause an assertion failure during recursive resolution     (CVE-2023-5679)

    * bind: Querying RFC 1918 reverse zones may cause an assertion failure when nxdomain-redirect is     enabled (CVE-2023-5517)

    * bind: Parsing large DNS messages may cause excessive CPU load (CVE-2023-4408)

    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.

The remote AlmaLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2024:1789 advisory.

  - The DNS message parsing code in `named` includes a section whose computational complexity is overly high.
    It does not cause problems for typical DNS traffic, but crafted queries and responses may cause excessive     CPU load on the affected `named` instance by exploiting this flaw. This issue affects both authoritative     servers and recursive resolvers. This issue affects BIND 9 versions 9.0.0 through 9.16.45, 9.18.0 through     9.18.21, 9.19.0 through 9.19.19, 9.9.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.45-S1, and 9.18.11-S1     through 9.18.21-S1. (CVE-2023-4408)

  - 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 flaw in query-handling code can cause `named` to exit prematurely with an assertion failure when: -     `nxdomain-redirect <domain>;` is configured, and - the resolver receives a PTR query for an RFC 1918     address that would normally result in an authoritative NXDOMAIN response. This issue affects BIND 9     versions 9.12.0 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.8-S1 through     9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1. (CVE-2023-5517)

  - A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure     during recursive resolution, when both of these features are enabled. This issue affects BIND 9 versions     9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.12-S1 through 9.16.45-S1,     and 9.18.11-S1 through 9.18.21-S1. (CVE-2023-5679)

  - To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to     clean up the database. It uses several methods, including some that are asynchronous: a small chunk of     memory pointing to the cache element that can be cleaned up is first allocated and then queued for later     processing. It was discovered that if the resolver is continuously processing query patterns triggering     this type of cache-database maintenance, `named` may not be able to handle the cleanup events in a timely     manner. This in turn enables the list of queued cleanup events to grow infinitely large over time,     allowing the configured `max-cache-size` limit to be significantly exceeded. This issue affects BIND 9     versions 9.16.0 through 9.16.45 and 9.16.8-S1 through 9.16.45-S1. (CVE-2023-6516)

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

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

    Bind-dyndb-ldap provides an LDAP back-end plug-in for BIND. It features support for dynamic updates and     internal caching, to lift the load off of your LDAP server.

    Security Fix(es):

    * bind9: Parsing large DNS messages may cause excessive CPU load (CVE-2023-4408)

    * bind9: Querying RFC 1918 reverse zones may cause an assertion failure when nxdomain-redirect is     enabled (CVE-2023-5517)

    * bind9: Enabling both DNS64 and serve-stale may cause an assertion failure during recursive resolution     (CVE-2023-5679)

    * bind9: Specific recursive query patterns may lead to an out-of-memory condition (CVE-2023-6516)

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

    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.

The remote Fedora 41 host has packages installed that are affected by multiple vulnerabilities as referenced in the FEDORA-2024-7378be30dd advisory.

    # Security Fixes

    -    Validating DNS messages containing a lot of DNSSEC signatures could cause excessive CPU load, leading     to a denial-of-service condition. This has been fixed.
    ([CVE-2023-50387](https://kb.isc.org/docs/cve-2023-50387))

        ISC would like to thank Elias Heftrig, Haya Schulmann, Niklas Vogel, and Michael Waidner from the     German National Research Center for Applied Cybersecurity ATHENE for bringing this vulnerability to our     attention. [GL #4424]

    -    Parsing DNS messages with many different names could cause excessive CPU load. This has been fixed.
    ([CVE-2023-4408](https://kb.isc.org/docs/cve-2023-4408))

        ISC would like to thank Shoham Danino from Reichman University, Anat Bremler-Barr from Tel-Aviv     University, Yehuda Afek from Tel-Aviv University, and Yuval Shavitt from Tel-Aviv University for bringing     this vulnerability to our attention. [GL #4234]

    -    Specific queries could cause named to crash with an assertion failure when nxdomain-redirect was     enabled. This has been fixed. ([CVE-2023-5517](https://kb.isc.org/docs/cve-2023-5517)) [GL #4281]

    -    A bad interaction between DNS64 and serve-stale could cause named to crash with an assertion failure,     when both of these features were enabled. This has been fixed.
    ([CVE-2023-5679](https://kb.isc.org/docs/cve-2023-5679)) [GL #4334]

    -  Under certain circumstances, the DNS-over-TLS client code incorrectly attempted to process more than     one DNS message at a time, which could cause named to crash with an assertion failure. This has been     fixed. [GL #4487]

    - Full [Release notes](https://downloads.isc.org/isc/bind9/9.18.24/doc/arm/html/notes.html#notes-for-     bind-9-18-24)

    ## Related blog post

    - [BIND 9 Security Release and Multi-Vendor Vulnerability Handling, CVE-2023-50387 and     CVE-2023-50868](https://www.isc.org/blogs/2024-bind-security-release/)


Tenable has extracted the preceding description block directly from the Fedora 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 Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-3974 advisory.

    -lts-announce@lists.debian.org     Subject: [SECURITY] [DLA 3974-1] dnsmasq security update

    - -------------------------------------------------------------------------     Debian LTS Advisory DLA-3974-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                          Lee Garrett     November 29, 2024                             https://wiki.debian.org/LTS
    - -------------------------------------------------------------------------

    Package        : dnsmasq     Version        : 2.85-1+deb11u1     CVE ID         : CVE-2022-0934 CVE-2023-28450 CVE-2023-50387 CVE-2023-50868     Debian Bug     :

    Brief introduction

    CVE-2022-0934

        A single-byte, non-arbitrary write/use-after-free flaw was found in dnsmasq.
        This flaw allows an attacker who sends a crafted packet processed by         dnsmasq, potentially causing a denial of service.

    CVE-2023-28450

        An issue was discovered in Dnsmasq before 2.90. The default maximum EDNS.0         UDP packet size was set to 4096 but should be 1232 because of DNS Flag Day         2020.

    CVE-2023-50387

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

        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.

    For Debian 11 bullseye, these problems have been fixed in version     2.85-1+deb11u1.

    We recommend that you upgrade your dnsmasq packages.

    For the detailed security status of dnsmasq please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/dnsmasq

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS

Tenable has extracted the preceding description block directly from the Debian 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 Redhat Enterprise Linux 6 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2025:0039 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: stack exhaustion in control channel code may lead to DoS (CVE-2023-3341)

    * bind9: Parsing large DNS messages may cause excessive CPU load (CVE-2023-4408)

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

    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.

The remote Alibaba Cloud Linux 3 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALINUX3-SA-2024:0027 advisory.

    Package updates are available for Alibaba Cloud Linux 3 that fix the following vulnerabilities:

    CVE-2022-3204:
    A vulnerability named 'Non-Responsive Delegation Attack' (NRDelegation Attack) has been discovered in     various DNS resolving software. The NRDelegation Attack works by having a malicious delegation with a     considerable number of non responsive nameservers. The attack starts by querying a resolver for a record     that relies on those unresponsive nameservers. The attack can cause a resolver to spend a lot of     time/resources resolving records under a malicious delegation point where a considerable number of     unresponsive NS records reside. It can trigger high CPU usage in some resolver implementations that     continually look in the cache for resolved NS records in that delegation. This can lead to degraded     performance and eventually denial of service in orchestrated attacks. Unbound does not suffer from high     CPU usage, but resources are still needed for resolving the malicious delegation. Unbound will keep trying     to resolve the record until hard limits are reached. Based on the nature of the attack and the replies,     different limits could be reached. From version 1.16.3 on, Unbound introduces fixes for better performance     when under load, by cutting opportunistic queries for nameserver discovery and DNSKEY prefetching and     limiting the number of times a delegation point can issue a cache lookup for missing records.

    CVE-2023-50387:
    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-50868:
    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.

Tenable has extracted the preceding description block directly from the Alibaba Cloud 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 remote Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-3859 advisory.

    - -------------------------------------------------------------------------     Debian LTS Advisory DLA-3859-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                          Adrian Bunk     September 02, 2024                            https://wiki.debian.org/LTS
    - -------------------------------------------------------------------------

    Package        : systemd     Version        : 247.3-7+deb11u6     CVE ID         : CVE-2023-7008 CVE-2023-50387 CVE-2023-50868     Debian Bug     : 1059278

    Multiple vulnerabilities have been fixed in systemd, the default init     system in Debian, when using systemd-resolved with DNSSEC.

    CVE-2023-7008

        Don't accept records of DNSSEC-signed domains when they have no signature.

    CVE-2023-50387

        DNSSEC denial of service (CPU consumption)

    CVE-2023-50868

        DNSSEC denial of service (CPU consumption)

    For Debian 11 bullseye, these problems have been fixed in version     247.3-7+deb11u6.

    We recommend that you upgrade your systemd packages.

    For the detailed security status of systemd please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/systemd

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS

Tenable has extracted the preceding description block directly from the Debian 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	名称	产品	系列	发布时间	最近更新时间	严重程度
190911	Fedora 39 : pdns-recursor (2024-b0f9656a76)	Nessus	Fedora Local Security Checks	2024/2/22	2024/11/14	high
190990	Fedora 38 : bind9-next (2024-c36c448396)	Nessus	Fedora Local Security Checks	2024/2/26	2025/3/31	high
191102	Ubuntu 20.04 LTS / 22.04 LTS / 23.10 : Unbound vulnerabilities (USN-6665-1)	Nessus	Ubuntu Local Security Checks	2024/2/28	2024/8/28	high
191110	AlmaLinux 8 : unbound (ALSA-2024:0965)	Nessus	Alma Linux Local Security Checks	2024/2/28	2024/2/28	high
191615	Amazon Linux 2023 : bind, bind-chroot, bind-devel (ALAS2023-2024-550)	Nessus	Amazon Linux Local Security Checks	2024/3/6	2024/12/11	high
192131	RHEL 8 : dnsmasq (RHSA-2024:1335)	Nessus	Red Hat Local Security Checks	2024/3/14	2024/11/7	high
192707	F5 Networks BIG-IP : DNS vulnerability (K000139092)	Nessus	F5 Networks Local Security Checks	2024/3/29	2024/10/3	high
192997	EulerOS 2.0 SP9 : bind (EulerOS-SA-2024-1502)	Nessus	Huawei Local Security Checks	2024/4/8	2024/4/8	high
193082	Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS : Bind vulnerabilities (USN-6723-1)	Nessus	Ubuntu Local Security Checks	2024/4/9	2024/8/27	high
193227	RHEL 9 : bind (RHSA-2024:1789)	Nessus	Red Hat Local Security Checks	2024/4/11	2024/11/7	high
193280	AlmaLinux 9 : bind (ALSA-2024:1789)	Nessus	Alma Linux Local Security Checks	2024/4/12	2024/7/26	high
193321	RHEL 9 : bind and bind-dyndb-ldap security updates (Important) (RHSA-2024:1800)	Nessus	Red Hat Local Security Checks	2024/4/15	2024/11/8	high
211316	Fedora 41 : bind / bind-dyndb-ldap (2024-7378be30dd)	Nessus	Fedora Local Security Checks	2024/11/14	2024/11/14	high
211973	Debian dla-3974 : dnsmasq - security update	Nessus	Debian Local Security Checks	2024/11/30	2024/11/30	high
213505	RHEL 6 : bind and bind-dyndb-ldap (RHSA-2025:0039)	Nessus	Red Hat Local Security Checks	2025/1/6	2025/6/5	high
236285	Alibaba Cloud Linux 3 : 0027: unbound (ALINUX3-SA-2024:0027)	Nessus	Alibaba Cloud Linux Local Security Checks	2025/5/14	2025/5/14	high
206418	Debian dla-3859 : libnss-myhostname - security update	Nessus	Debian Local Security Checks	2024/9/2	2024/9/2	medium

检测

插件搜索

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

medium