[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPZ8mV610770z8PMHf8qoM+abxf=2rueX_HTji0RwQvZfRE-3g@mail.gmail.com>
Date: Mon, 22 Aug 2011 12:38:28 -0700
From: Mark Doliner <mark@...gant.net>
To: Moritz Mühlenhoff <jmm@...til.org>
Cc: oss-security@...ts.openwall.com
Subject: Re: CVE request: Pidgin crash
2011/8/22 Moritz Mühlenhoff <jmm@...til.org>:
> On Mon, Aug 22, 2011 at 02:55:34AM -0400, Huzaifa Sidhpurwala wrote:
>> Hi Mark,
>>
>> >Hi! Would it be possible to issue a CVE for a new crash in Pidgin?
>>
>> >http://pidgin.im/news/security/?id=53
>>
>> Please use CVE-2011-2942 for this issue.
>>
>> Also looking at http://pidgin.im/news/security it seems two other security issues were also
>> fixed in 2.10.0, do you want CVEs to be assigned for them as well?
>
> Please do. Since they're published in the form of upstream advisories
> we'd like to properly track them in the Debian Security Tracker.
That's fine by me. As an upstream developer I don't feel like I have
a strong incentive to obtain a CVE. But if it's helpful to packagers,
than sure.
The two issues in question are discussed here:
http://pidgin.im/news/security/?id=54
http://pidgin.im/news/security/?id=55
The second one only affects Pidgin on Microsoft Windows.
--Mark
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.
