Bug 231282 - net-dns/dnsmasq possibly affected by cache poisoning issue VU#800113 ?
|
Bug#:
231282
|
Product: Gentoo Security
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: security@gentoo.org
|
Reported By: vorlon@gentoo.org
|
|
Component: Vulnerabilities
|
|
|
URL:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2008q3/002147.html
|
|
Summary: net-dns/dnsmasq possibly affected by cache poisoning issue VU#800113 ?
|
|
Keywords:
|
|
Status Whiteboard: ?? [glsa]
|
|
Opened: 2008-07-09 10:48 0000
|
dnsmasq is probably affected by the cache poisoning issues too, see $URL
Yes, it does appear to be affected, I will update the version in portage as
soon as a fix is out.
I've tested both versions. I noticed that in the recently committed version
that dnsmasq doesn't leave a high numbered UDP port open (in my case it was
32781)
output of netstat -an | grep udp
Version 2.42:
udp 0 0 0.0.0.0:32781 0.0.0.0:*
udp 0 0 0.0.0.0:53 0.0.0.0:*
Version 2.43rc3:
udp 0 0 0.0.0.0:53 0.0.0.0:*
Arches, please test and mark stable:
=net-dns/dnsmasq-2.43
Target keywords : "alpha amd64 arm hppa ia64 ppc ppc64 s390 sh sparc x86"
Since bind got a GLSA, I guess we'll have another one, but maybe we should
combine with other DNS resolvers? Anyway, glsa reques filed.