rpm package
almalinux/dnsmasq-utils
pkg:rpm/almalinux/dnsmasq-utils
Vulnerabilities (11)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-5172 | Hig | 7.3 | < 2.90-7.el10_2 | 2.90-7.el10_2 | May 11, 2026 | A buffer overflow in dnsmasq’s extract_addresses() function allows an attacker to trigger a heap out-of-bounds read and crash by exploiting a malformed DNS response, enabling extract_name() to advance the pointer past the record’s end. | |
| CVE-2026-4893 | Med | 5.3 | < 2.90-7.el10_2 | 2.90-7.el10_2 | May 11, 2026 | An information disclosure vulnerability in dnsmasq allows remote attackers to bypass source checks via a crafted DNS packet with RFC 7871 client subnet information. | |
| CVE-2026-4892 | Hig | 8.4 | < 2.90-7.el10_2 | 2.90-7.el10_2 | May 11, 2026 | A heap-based out-of-bounds write vulnerability in the DHCPv6 implementation of dnsmasq allows local attackers to execute arbitrary code with root privileges via a crafted DHCPv6 packet. | |
| CVE-2026-4891 | Med | 5.3 | < 2.90-7.el10_2 | 2.90-7.el10_2 | May 11, 2026 | A heap-based out-of-bounds read vulnerability in the DNSSEC validation of dnsmasq allows remote attackers to cause a denial of service via a crafted DNS packet. | |
| CVE-2026-4890 | Hig | 7.5 | < 2.90-7.el10_2 | 2.90-7.el10_2 | May 11, 2026 | A Denial of Service (DoS) vulnerability in the DNSSEC validation of dnsmasq allows remote attackers to cause a denial of service via a crafted DNS packet. | |
| CVE-2026-2291 | Hig | 7.3 | < 2.90-7.el10_2 | 2.90-7.el10_2 | May 11, 2026 | dnsmasqs extract_name() function can be abused to cause a heap buffer overflow, allowing an attacker to inject false DNS cache entries, which could result in DNS lookups to redirect to an attacker-controlled IP address, or to cause a DoS. | |
| CVE-2023-50868 | — | < 2.85-14.el9_3.1 | 2.85-14.el9_3.1 | Feb 14, 2024 | 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 51 | ||
| CVE-2023-50387 | — | < 2.85-14.el9_3.1 | 2.85-14.el9_3.1 | Feb 14, 2024 | 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 man | ||
| CVE-2023-28450 | — | < 2.85-14.el9 | 2.85-14.el9 | Mar 15, 2023 | 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-2022-0934 | — | < 2.79-24.el8 | 2.79-24.el8 | Aug 29, 2022 | 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-2021-3448 | — | < 2.79-19.el8 | 2.79-19.el8 | Apr 8, 2021 | 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 ran |
- affected < 2.90-7.el10_2fixed 2.90-7.el10_2
A buffer overflow in dnsmasq’s extract_addresses() function allows an attacker to trigger a heap out-of-bounds read and crash by exploiting a malformed DNS response, enabling extract_name() to advance the pointer past the record’s end.
- affected < 2.90-7.el10_2fixed 2.90-7.el10_2
An information disclosure vulnerability in dnsmasq allows remote attackers to bypass source checks via a crafted DNS packet with RFC 7871 client subnet information.
- affected < 2.90-7.el10_2fixed 2.90-7.el10_2
A heap-based out-of-bounds write vulnerability in the DHCPv6 implementation of dnsmasq allows local attackers to execute arbitrary code with root privileges via a crafted DHCPv6 packet.
- affected < 2.90-7.el10_2fixed 2.90-7.el10_2
A heap-based out-of-bounds read vulnerability in the DNSSEC validation of dnsmasq allows remote attackers to cause a denial of service via a crafted DNS packet.
- affected < 2.90-7.el10_2fixed 2.90-7.el10_2
A Denial of Service (DoS) vulnerability in the DNSSEC validation of dnsmasq allows remote attackers to cause a denial of service via a crafted DNS packet.
- affected < 2.90-7.el10_2fixed 2.90-7.el10_2
dnsmasqs extract_name() function can be abused to cause a heap buffer overflow, allowing an attacker to inject false DNS cache entries, which could result in DNS lookups to redirect to an attacker-controlled IP address, or to cause a DoS.
- CVE-2023-50868Feb 14, 2024affected < 2.85-14.el9_3.1fixed 2.85-14.el9_3.1
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 51
- CVE-2023-50387Feb 14, 2024affected < 2.85-14.el9_3.1fixed 2.85-14.el9_3.1
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 man
- CVE-2023-28450Mar 15, 2023affected < 2.85-14.el9fixed 2.85-14.el9
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-2022-0934Aug 29, 2022affected < 2.79-24.el8fixed 2.79-24.el8
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-2021-3448Apr 8, 2021affected < 2.79-19.el8fixed 2.79-19.el8
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 ran