Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Sun, 22 Feb 2015 13:25:20 +0100
From: Salvatore Bonaccorso <>
Subject: Re: heap overflow in procmail

Hi MITRE team,

On Thu, Feb 12, 2015 at 03:14:10PM +0100, Jakub Wilk wrote:
> >>
> [...]
> >The Debian bug report does not contain diagnosis of the type of
> >programming error that is triggering each crash, so it is not clear how
> >many CVE identifiers must be assigned.
> There are two distinct buffer overflows:
> * Off-by-one heap overflow when parsing addresses that have left angle
> bracket, then a comma, but no right angle bracket. For example:
> <,
> * Heap overflow when parsing addresses that end with backslash. For example:
> <\
> Credit goes to Jan Darmochwal for identifying the root causes.

Not sure if this got lost, so just reasking. Can you assing CVEs based
on the above? (actually one or two CVEs?)


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.