[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <504E1162.6000405@redhat.com>
Date: Mon, 10 Sep 2012 18:12:18 +0200
From: Florian Weimer <fweimer@...hat.com>
To: oss-security@...ts.openwall.com
CC: Kurt Seifried <kseifried@...hat.com>, Jan Lieskovsky <jlieskov@...hat.com>,
"Steven M. Christey" <coley@...us.mitre.org>,
Jeff Law <law@...hat.com>, Jakub Jelinek <jakub@...hat.com>
Subject: Re: CVE Request -- glibc: strcoll() integer overflow
leading to buffer overflow + another alloca() stack overflow issue (upstream
#14547 && #14552)
On 09/07/2012 07:21 PM, Kurt Seifried wrote:
>> 2) Issue #2 (mentioned here only for completeness, but I am not of
>> the opinion this should receive a CVE identifier. See argumentation
>> below [but open to glibc upstream / others to disprove it]).
>
> I will hold off on issuing a CVE for this then. Anyone want to weigh in?
It looks as if the alloca issue was introduced at the same time as the
malloc-related overflow:
http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=5358d026c74
So perhaps one CVE is enough for glibc bugs 14552 and 14547 because the
problems are similar and affect the same versions.
--
Florian Weimer / Red Hat Product Security 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.
