oss-sec mailing list archives
Re: heap overflow in procmail
From: Salvatore Bonaccorso <carnil () debian org>
Date: Sun, 22 Feb 2015 13:25:20 +0100
Hi MITRE team, On Thu, Feb 12, 2015 at 03:14:10PM +0100, Jakub Wilk wrote:
https://bugs.debian.org/769937[...]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: <moo () example com, * Heap overflow when parsing addresses that end with backslash. For example: <moo () example com\ 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?) Regards, Salvatore
Current thread:
- Re: heap overflow in procmail Jakub Wilk (Jan 21)
- Re: heap overflow in procmail cve-assign (Jan 22)
- Re: heap overflow in procmail Jakub Wilk (Feb 12)
- Re: heap overflow in procmail Salvatore Bonaccorso (Feb 22)
- Re: heap overflow in procmail Jakub Wilk (Feb 12)
- Re: heap overflow in procmail Salvatore Bonaccorso (Feb 11)
- Re: heap overflow in procmail cve-assign (Jan 22)