[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <547FA641.8080306@fixme.fi>
Date: Thu, 04 Dec 2014 02:09:37 +0200
From: Tero Marttila <terom@...me.fi>
To: "Joshua J. Drake" <oss-sec-pmgetbl@...p.org>,
oss-security@...ts.openwall.com
CC: Santiago Vila <sanvila@...ian.org>
Subject: Re: CVE request: procmail heap overflow in getlline()
FWIW I don't have a specific PoC/scenario to supply for this case that
serves as an exploit with untrusted input, but I am not familar enough
with procmail and how it is used to make a judgement on if some related
code-path/scenario could be exploitable.
I reported this as a security bug due to the implied high risk level of
procmail being suid-root on Debian, and thus deserving of more detailed
inspection. But that's a distribution issue.
-- Tero Marttila
On 04/12/14 01:30, Joshua J. Drake wrote:
> Is it possible to trigger this issue with untrusted input or only
> trusted input from procmailrc?
>
> Joshua
>
> On Wed, Dec 03, 2014 at 11:31:20PM +0200, Henri Salo wrote:
>> Please assign 2014 CVE for procmail heap overflow in getlline() as described in
>> following Debian BTS item <https://bugs.debian.org/771958> reported by Tero
>> Marttila. Please comment if you need more information about the issue.
>>
>> ---
>> Henri Salo
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.
