Описание
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.
A flaw was found in Dnsmasq. The default maximum EDNS.0 UDP packet size was set to 4096 but should be 1232 because of DNS Flag Day 2020.
Отчет
The severity of this vulnerability is not important but moderate because exploiting the vulnerability can lead to a theoretical disruption of the availability of the service, but doesn’t directly compromise data integrity or confidentiality. This theoretical disruption would require an attacker to be able to induce IP fragmentation during transmission and can be mitigated with a simple configuration change in any affected version. A successful attack would require significant target specific preparation and the ability to act as a man-in-the-middle or control the path MTU of the authoritative DNS server. Additionally, this CVE is easily remediated by setting the edns-packet-max value to 1232 in the dnsmasq configuration. The changes made for DNS Flag Day 2020 were primarily related to improving service reliability in order to make sure that DNS servers do not experience transmission failures due to IP fragmentation over networks of unknown MTU configurations. This change of the default maximum EDNS Buffer Size was coordinated so that default configurations of DNS services would provide more reliable default settings as well as avoid attacks on DNS services that can only be made possible when UDP packets are fragmented in transit. For example, if the DNS Query ID and UDP port are carried in the first IP fragment, an attacker could spoof the second fragment and poison the DNS cache by swapping the subsequent good IP fragments with their own. By using a default maximum EDNS value of 1232 (the largest value found to avoids fragmentation on nearly all modern networks) and relying on TCP for DNS queries with larger responses, IP Fragmentation issues can be reliably avoided with the default dnsmasq configuration.
Меры по смягчению последствий
Systems that can not be updated can still configure dnsmasq to use the recommended maximum EDNS value by setting edns-packet-max=1232 in the dnsmasq configuration.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 6 | dnsmasq | Out of support scope | ||
| Red Hat Enterprise Linux 7 | dnsmasq | Out of support scope | ||
| Red Hat OpenStack Platform 13 (Queens) | dnsmasq | Out of support scope | ||
| Red Hat Enterprise Linux 8 | dnsmasq | Fixed | RHSA-2023:7046 | 14.11.2023 |
| Red Hat Enterprise Linux 8.6 Extended Update Support | dnsmasq | Fixed | RHSA-2024:1545 | 27.03.2024 |
| Red Hat Enterprise Linux 8.8 Extended Update Support | dnsmasq | Fixed | RHSA-2024:1544 | 27.03.2024 |
| Red Hat Enterprise Linux 9 | dnsmasq | Fixed | RHSA-2023:6524 | 07.11.2023 |
| Red Hat Enterprise Linux 9.2 Extended Update Support | dnsmasq | Fixed | RHSA-2024:4052 | 23.06.2024 |
Показывать по
Дополнительная информация
Статус:
EPSS
7.5 High
CVSS3
Связанные уязвимости
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.
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.
An issue was discovered in Dnsmasq before 2.90. The default maximum ED ...
EPSS
7.5 High
CVSS3