From ${URL} : The following flaw was found in dnsmasq: Dnsmasq does not properly check the return value of the setup_reply() function called during a tcp connection (by the tcp_request() function). This return value is then used as a size argument in a function which writes data on the client's connection. This may lead, upon successful exploitation, to reading the heap memory of dnsmasq. This issue is fixed in dnsmasq-2.73rc4: http://www.thekelleys.org.uk/dnsmasq/release-candidates/ External References: https://www.obrela.com/home/security-labs/advisories/osi-advisory-osi-1502/ @maintainer(s): after the bump, in case we need to stabilize the package, please let us know if it is ready for the stabilization or not.
Pulled in fix from git to dnsmasq-2.72-r1, it is ready for stabilization.
CVE-2015-3294 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-3294): The tcp_request function in Dnsmasq before 2.73rc4 does not properly handle the return value of the setup_reply function, which allows remote attackers to read process memory and cause a denial of service (out-of-bounds read and crash) via a malformed DNS request.
(In reply to Patrick McLean from comment #1) > Pulled in fix from git to dnsmasq-2.72-r1, it is ready for stabilization. This was missed, do you still want to stable dnsmasq-2.72-r1 or later version as there are two later in tree.
Use 2.72-r2 since 2.73 is too new to be stabilized yet, and the only change from -r1 to -r2 is a lua dependency tweak.
Arches, please stabilize: =net-dns/dnsmasq-2.72-r1 Stable targets: alpha amd64 arm hppa ia64 ppc ppc64 sparc x86
(In reply to Kristian Fiskerstrand from comment #5) > Arches, please stabilize: > =net-dns/dnsmasq-2.72-r1 > Stable targets: alpha amd64 arm hppa ia64 ppc ppc64 sparc x86 Sorry, misread, that should be =net-dns/dnsmasq-2.72-r2 Stable targets: alpha amd64 arm hppa ia64 ppc ppc64 sparc x86
amd64 stable
x86 stable
sparc stable
arm stable
Stable for HPPA.
Stable for PPC64.
ppc stable
alpha stable
ia64 stable
Arches, Thank you for your work. Maintainer(s), please drop the vulnerable version(s). New GLSA Request filed.
It has been 30 days+ since cleanup requested. Maintainer(s), please drop the vulnerable version(s).
This issue was resolved and addressed in GLSA 201512-01 at https://security.gentoo.org/glsa/201512-01 by GLSA coordinator Yury German (BlueKnight).
Re-Openning for Cleanup
Maintainer(s), please drop the vulnerable version(s).
Can we please clean up version =net-dns/dnsmasq-2.66 please. Vulnerable since last year.
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=82c65b45c21f0c64aaf06ced2177d58685caf9ac
