CVE-2020-25683

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.

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.

Se encontró un fallo en dnsmasq versiones anteriores a 2.83. Se detectó un desbordamiento del búfer en la región heap de la memoria en dnsmasq cuando DNSSEC está habilitado y antes de comprobar las entradas DNS recibidas. Un atacante remoto, que puede crear respuestas DNS válidas, podría usar este fallo para causar un desbordamiento en una memoria asignada de la pila. Este fallo es causado por una falta de comprobación de longitud en rfc1035.c:extract_name(), que podría ser abusado para causar que el código ejecute memcpy() con un tamaño negativo en get_rdata() y causar un bloqueo en dnsmasq, lo que resultaría en una denegación de servicio. La mayor amenaza de esta vulnerabilidad es la disponibilidad del sistema