The remote SUSE Linux SLES12 / SLES_SAP12 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:1289-1 advisory.

  - A flaw was found in dnsmasq in versions before 2.85. When configured to use a specific server for a given     network interface, dnsmasq uses a fixed port while forwarding queries. An attacker on the network, able to     find the outgoing port used by dnsmasq, only needs to guess the random transmission ID to forge a reply     and get it accepted by dnsmasq. This flaw makes a DNS Cache Poisoning attack much easier. The highest     threat from this vulnerability is to data integrity. (CVE-2021-3448)

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

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

An update of the dnsmasq package has been released.

  - A flaw was found in dnsmasq in versions before 2.85. When configured to use a specific server for a given     network interface, dnsmasq uses a fixed port while forwarding queries. An attacker on the network, able to     find the outgoing port used by dnsmasq, only needs to guess the random transmission ID to forge a reply     and get it accepted by dnsmasq. This flaw makes a DNS Cache Poisoning attack much easier. The highest     threat from this vulnerability is to data integrity. (CVE-2021-3448)

Note that Nessus has not tested for this issue 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 a vulnerability as referenced in the ALSA-2021:4153 advisory.

  - A flaw was found in dnsmasq in versions before 2.85. When configured to use a specific server for a given     network interface, dnsmasq uses a fixed port while forwarding queries. An attacker on the network, able to     find the outgoing port used by dnsmasq, only needs to guess the random transmission ID to forge a reply     and get it accepted by dnsmasq. This flaw makes a DNS Cache Poisoning attack much easier. The highest     threat from this vulnerability is to data integrity. (CVE-2021-3448)

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

Simon Kelley reports :

[In configurations where the forwarding server address contains an @ character for specifying a sending interface or source address, the] random source port behavior was disabled, making cache poisoning attacks possible.

This only affects configurations of the form server=1.1.1.1@em0 or server=1.1.1.1@192.0.2.1, i. e. those that specify an interface to send through, or an IP address to send from, or use together with NetworkManager.

New dnsmasq packages are available for Slackware 14.0, 14.1, 14.2, and -current to fix a security issue.

The remote Ubuntu 18.04 LTS / 20.04 LTS / 21.04 host has packages installed that are affected by a vulnerability as referenced in the USN-4976-1 advisory.

  - A flaw was found in dnsmasq in versions before 2.85. When configured to use a specific server for a given     network interface, dnsmasq uses a fixed port while forwarding queries. An attacker on the network, able to     find the outgoing port used by dnsmasq, only needs to guess the random transmission ID to forge a reply     and get it accepted by dnsmasq. This flaw makes a DNS Cache Poisoning attack much easier. The highest     threat from this vulnerability is to data integrity. (CVE-2021-3448)

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 version of the dnsmasq package installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerability :

  - A flaw was found in dnsmasq in versions before 2.85.
    When configured to use a specific server for a given     network interface, dnsmasq uses a fixed port while     forwarding queries. An attacker on the network, able to     find the outgoing port used by dnsmasq, only needs to     guess the random transmission ID to forge a reply and     get it accepted by dnsmasq. This flaw makes a DNS Cache     Poisoning attack much easier. The highest threat from     this vulnerability is to data integrity.(CVE-2021-3448)

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 6.06, has dnsmasq packages installed that are affected by multiple vulnerabilities:

  - A flaw was found in dnsmasq before version 2.83. A heap-based buffer overflow was discovered in the way     RRSets are sorted before validating with DNSSEC data. An attacker on the network, who can forge DNS     replies such as that they are accepted as valid, could use this flaw to cause a buffer overflow with     arbitrary data in a heap memory segment, possibly executing code on the machine. The highest threat from     this vulnerability is to data confidentiality and integrity as well as system availability.
    (CVE-2020-25681)

  - A flaw was found in dnsmasq before 2.83. A buffer overflow vulnerability was discovered in the way dnsmasq     extract names from DNS packets before validating them with DNSSEC data. An attacker on the network, who     can create valid DNS replies, could use this flaw to cause an overflow with arbitrary data in a heap-     allocated memory, possibly executing code on the machine. The flaw is in the rfc1035.c:extract_name()     function, which writes data to the memory pointed by name assuming MAXDNAME*2 bytes are available in the     buffer. However, in some code execution paths, it is possible extract_name() gets passed an offset from     the base buffer, thus reducing, in practice, the number of available bytes that can be written in the     buffer. The highest threat from this vulnerability is to data confidentiality and integrity as well as     system availability. (CVE-2020-25682)

  - A flaw was found in dnsmasq before version 2.83. A heap-based buffer overflow was discovered in dnsmasq     when DNSSEC is enabled and before it validates the received DNS entries. A remote attacker, who can create     valid DNS replies, could use this flaw to cause an overflow in a heap-allocated memory. This flaw is     caused by the lack of length checks in rfc1035.c:extract_name(), which could be abused to make the code     execute memcpy() with a negative size in get_rdata() and cause a crash in dnsmasq, resulting in a denial     of service. The highest threat from this vulnerability is to system availability. (CVE-2020-25683)

  - A flaw was found in dnsmasq before version 2.83. When getting a reply from a forwarded query, dnsmasq     checks in the forward.c:reply_query() if the reply destination address/port is used by the pending     forwarded queries. However, it does not use the address/port to retrieve the exact forwarded query,     substantially reducing the number of attempts an attacker on the network would have to perform to forge a     reply and get it accepted by dnsmasq. This issue contrasts with RFC5452, which specifies a query's     attributes that all must be used to match a reply. This flaw allows an attacker to perform a DNS Cache     Poisoning attack. If chained with CVE-2020-25685 or CVE-2020-25686, the attack complexity of a successful     attack is reduced. The highest threat from this vulnerability is to data integrity. (CVE-2020-25684)

  - A flaw was found in dnsmasq before version 2.83. When getting a reply from a forwarded query, dnsmasq     checks in forward.c:reply_query(), which is the forwarded query that matches the reply, by only using a     weak hash of the query name. Due to the weak hash (CRC32 when dnsmasq is compiled without DNSSEC, SHA-1     when it is) this flaw allows an off-path attacker to find several different domains all having the same     hash, substantially reducing the number of attempts they would have to perform to forge a reply and get it     accepted by dnsmasq. This is in contrast with RFC5452, which specifies that the query name is one of the     attributes of a query that must be used to match a reply. This flaw could be abused to perform a DNS Cache     Poisoning attack. If chained with CVE-2020-25684 the attack complexity of a successful attack is reduced.
    The highest threat from this vulnerability is to data integrity. (CVE-2020-25685)

  - A flaw was found in dnsmasq before version 2.83. When receiving a query, dnsmasq does not check for an     existing pending request for the same name and forwards a new request. By default, a maximum of 150     pending queries can be sent to upstream servers, so there can be at most 150 queries for the same name.
    This flaw allows an off-path attacker on the network to substantially reduce the number of attempts that     it would have to perform to forge a reply and have it accepted by dnsmasq. This issue is mentioned in the     Birthday Attacks section of RFC5452. If chained with CVE-2020-25684, the attack complexity of a     successful attack is reduced. The highest threat from this vulnerability is to data integrity.
    (CVE-2020-25686)

  - A flaw was found in dnsmasq before version 2.83. A heap-based buffer overflow was discovered in dnsmasq     when DNSSEC is enabled and before it validates the received DNS entries. This flaw allows a remote     attacker, who can create valid DNS replies, to cause an overflow in a heap-allocated memory. This flaw is     caused by the lack of length checks in rfc1035.c:extract_name(), which could be abused to make the code     execute memcpy() with a negative size in sort_rrset() and cause a crash in dnsmasq, resulting in a denial     of service. The highest threat from this vulnerability is to system availability. (CVE-2020-25687)

  - A flaw was found in dnsmasq in versions before 2.85. When configured to use a specific server for a given     network interface, dnsmasq uses a fixed port while forwarding queries. An attacker on the network, able to     find the outgoing port used by dnsmasq, only needs to guess the random transmission ID to forge a reply     and get it accepted by dnsmasq. This flaw makes a DNS Cache Poisoning attack much easier. The highest     threat from this vulnerability is to data integrity. (CVE-2021-3448)

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
160071	SUSE SLES12 Security Update : dnsmasq (SUSE-SU-2022:1289-1)	Nessus	SuSE Local Security Checks	4/22/2022	7/13/2023	medium
153039	Photon OS 4.0: Dnsmasq PHSA-2021-4.0-0093	Nessus	PhotonOS Local Security Checks	9/7/2021	12/1/2023	medium
157663	AlmaLinux 8 : dnsmasq (ALSA-2021:4153)	Nessus	Alma Linux Local Security Checks	2/9/2022	11/10/2023	medium
147874	FreeBSD : dnsmasq -- cache poisoning vulnerability in certain configurations (5b72b1ff-877c-11eb-bd4f-2f1d57dafe46)	Nessus	FreeBSD Local Security Checks	3/18/2021	1/9/2024	medium
148500	Slackware 14.0 / 14.1 / 14.2 / current : dnsmasq (SSA:2021-102-01)	Nessus	Slackware Local Security Checks	4/14/2021	1/4/2024	medium
150143	Ubuntu 18.04 LTS / 20.04 LTS : Dnsmasq vulnerability (USN-4976-1)	Nessus	Ubuntu Local Security Checks	6/2/2021	10/16/2023	medium
151555	EulerOS Virtualization 2.9.0 : dnsmasq (EulerOS-SA-2021-2199)	Nessus	Huawei Local Security Checks	7/13/2021	12/8/2023	medium
187345	NewStart CGSL MAIN 6.06 : dnsmasq Multiple Vulnerabilities (NS-SA-2023-0078)	Nessus	NewStart CGSL Local Security Checks	12/27/2023	12/28/2023	high

Detections

Analytics

Plugins Search

medium

medium

medium

medium

medium

medium

medium

high