Date: Mon, 26 Mar 2012 12:48:56 -0600 From: Kurt Seifried <kseifried@...hat.com> To: oss-security@...ts.openwall.com CC: Jan Lieskovsky <jlieskov@...hat.com>, "Steven M. Christey" <coley@...us.mitre.org>, Florian Weimer <fw@...eb.enyo.de>, smcv@...ian.org Subject: Re: CVE-2010 Request: quake3 / openarena-server: DDoS by processing 'getstatus' and 'rcon' packets On 03/26/2012 07:09 AM, Jan Lieskovsky wrote: > Hello Kurt, Steve, vendors, > > yet in 2010 the following problem has been corrected in Quake3 / > OpenArena: > > A distributed denial of service flaw was found in the way Quake3 Arena / > OpenArena servers used to handle 'getstatus' and 'rcon' (remote command) > connectionless requests. A remote attacker could use this flaw to perform > distributed denial of service attack against the target server IP > gameserver by > spoofing certain packets. > > References: >  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665656 >  http://openarena.ws/board/index.php?topic=4391.0 >  http://www.ioquake.org/forums/viewtopic.php?f=12&t=1694 >  http://www.urbanterror.info/forums/topic/27825-drdos/ >  > http://lists.ioquake.org/pipermail/ioquake3-ioquake.org/2012-January/004778.html > >  https://bugzilla.redhat.com/show_bug.cgi?id=806898 > > Relevant upstream patch: >  http://icculus.org/pipermail/quake3-commits/2010-January/001679.html > > Could you allocate a CVE-2010-* CVE identifier for this issue? > > Thank you && Regards, Jan. > -- > Jan iankko Lieskovsky / Red Hat Security Response Team > > P.S.: There doesn't seem to be a CVE identifier for this issue yet: > http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=quake3 > > mentions various Quake3 related security flaws, but doesn't > this concrete issue yet. Please use CVE-2010-5077 for this issue. -- Kurt Seifried Red Hat Security Response Team (SRT)
Powered by blists - more mailing lists
Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.