In dnsmasq before 2.78, if the DNS packet size does not match the expected size, the size parameter in a memset call…
No fixed version listed yet.Check the vendor advisory. References ↓
The flaw lies in dnsmasq before 2.78, in the handling of DNS packets whose size does not match the expected size, where a size parameter passed to a memset call becomes negative. Because that value is treated as unsigned, memset writes a very large number of zero bytes, causing dnsmasq to crash.
Official description · CVE.org
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.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 2 Oct 2017. No public exploit code or confirmed exploitation is recorded.