|
Message-ID: <4E25B0C5.5010306@redhat.com> Date: Tue, 19 Jul 2011 18:28:53 +0200 From: Jan Lieskovsky <jlieskov@...hat.com> To: Alan Boudreault <aboudreault@...gears.com>, Even Rouault <even.rouault@...es-paris.org> CC: oss-security@...ts.openwall.com, "Steven M. Christey" <coley@...us.mitre.org>, Pavel Lisý <pavel.lisy@...il.com> Subject: CVE Request -- MapServer -- Stack based buffer overflow [was: Re: Re: CVE Request -- MapServer -- SQL injections in OGC filter encoding and in WMS time support.] Alan, Even, thanks for your replies. Just to clarify this one a bit yet. Two CVE identifiers (one for the multiple SQL injection flaws, the other for the stack based buffer overflow issue) seem to be necessary in this case (due different versions affected): [1] http://lists.osgeo.org/pipermail/mapserver-users/2011-July/069430.html Thank you && Regards, Jan. -- Jan iankko Lieskovsky / Red Hat Security Response Team On 07/19/2011 05:32 PM, Alan Boudreault wrote: > I got new from the debian security guy yesterday. I should get the CVE id > soon. > > Thanks, > Alan > > On July 19, 2011 11:28:29 am Even Rouault wrote: >> Selon Jan Lieskovsky<jlieskov@...hat.com>: >> >> Jan, >> >> I believe Alan Boudreault (MapServer team member that I've added to the CC >> list) has already asked the Debian security team to request for a CVE >> number, but without any result for now. Maybe he can confirm. >> >> Best regards, >> >> Even >> >>> Hello Josh, Steve, vendors, >>> >>> the following has been brought to our attention: >>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=722545 >>> [2] http://trac.osgeo.org/mapserver/ticket/3903 >>> >>> More from [2]: >>> >>> This ticket is to track fixes to prevent SQL injections through OGC >>> filter encoding (in WMS, WFS and SOS), as well as a potential SQL >>> injection in WMS time support. >>> >>> Your system may be vulnerable if it has MapServer with OGC protocols >>> enabled, with layers connecting to an SQL RDBMS backend, either natively >>> or via OGR. >>> >>> All versions of MapServer 4.x, 5.x and 6.x are potentially vulnerable. >>> All users are ** strongly encouraged ** to upgrade to one of the latest >>> releases with the fixes. >>> >>> Could you allocate a CVE id for this? >>> >>> Thank you&& Regards, Jan. >>> -- >>> Jan iankko Lieskovsky / Red Hat Security Response Team >
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.