found 578583 1.5.21-1 tag 578583 +confirmed pending thanks On Thu, Dec 30, 2010 at 10:10:08PM +0100, Marcin Szewczyk wrote: > On Thu, Dec 30, 2010 at 04:31:58PM +0000, Antonio Radici wrote: > > it seems that this bug is not reproducible on 1.5.20-9, I'm therefore > > closing this bug, if it's not the case please feel free to reopen. > > I'm still able to reproduce it on 1.5.20-9. And I've got a confirmation > from a friend that version 1.5.21-1 is also affected. > > So these are the steps which lead to a segfault: > 1) Unpack an evil Maildir (attached to this message) > 2) Run /usr/bin/mutt -f maildir-segfault > 3) Open the message > 4) press 'h' > 5) SEGV >
Hi Marcin, sorry for closing the wrong bug, now I'm able to reproduce the problem. It is pretty similar to #578087 (i.e.: no check on strchr() return value), I will prepare a patch to be included in 1.5.21-2 and I'll forward it upstream. This will be certainly fixed in the next release, setting the bug in pending. Sorry again for closing the bug too quickly. Cheers Antonio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
