CVE-2020-25687: Buffer Overflow
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:extractname(), which could be abused to make the code execute memcpy() with a negative size in sortrrset() and cause a crash in dnsmasq, resulting in a denial of service. The highest threat from this vulnerability is to system availability.
Other sources
An 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:extractname(), which could be abused to make the code execute memcpy() with negative size in sortrrset(), which is interpreted as huge numbers.
— Red Hat
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is CVE-2020-25687?
CVE-2020-25687 is a vulnerability in dnsmasq before version 2.83 that allows a remote attacker to cause a heap-based buffer overflow.
How does CVE-2020-25687 affect dnsmasq?
CVE-2020-25687 affects dnsmasq when DNSSEC is enabled and before it validates the received DNS entries.
What is the severity of CVE-2020-25687?
The severity of CVE-2020-25687 is high, with a severity value of 5.9.
Which software versions are affected by CVE-2020-25687?
Dnsmasq versions before 2.83 are affected by CVE-2020-25687.
How can I mitigate CVE-2020-25687?
To mitigate CVE-2020-25687, it is recommended to update dnsmasq to version 2.83 or later.