First published: Mon Oct 02 2017(Updated: )
In dnsmasq before 2.78, if the DNS packet size does not match the expected size, the size parameter in a memset call gets a negative value. As it is an unsigned value, memset ends up writing up to 0xffffffff zero's (0xffffffffffffffff in 64 bit platforms), making dnsmasq crash.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Ubuntu | =14.04 | |
Ubuntu | =16.04 | |
Ubuntu | =17.04 | |
Debian | =7.0 | |
Debian | =7.1 | |
Debian | =9.0 | |
Fedora | =27 | |
openSUSE | =42.2 | |
openSUSE | =42.3 | |
Red Hat Enterprise Linux Desktop | =7.0 | |
Red Hat Enterprise Linux Server | =7.0 | |
Red Hat Enterprise Linux Workstation | =7.0 | |
Dnsmasq | <=2.77 |
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=63437ffbb58837b214b4b92cb1c54bc5f3279928
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-13704 has been classified as a high severity vulnerability due to its ability to cause a crash in dnsmasq.
To fix CVE-2017-13704, update dnsmasq to version 2.78 or later.
CVE-2017-13704 affects various versions of dnsmasq prior to 2.78 on systems like Ubuntu, Debian, Fedora, and Red Hat.
CVE-2017-13704 exploits improper handling of DNS packet sizes, leading to a crash due to an erroneous memset call.
As a temporary workaround for CVE-2017-13704, consider restricting external DNS queries or disabling the dnsmasq service until an update can be applied.