Re: [Mutt] #2033: buffer overflow in attachment decoding function

#2033: buffer overflow in attachment decoding function ---+ Reporter: pvalc...@openbsd.org | Owner: mutt-dev Type: defect| Status: closed

Re: [Mutt] #2033: buffer overflow in attachment decoding function

#2033: buffer overflow in attachment decoding function Comment (by Peter Valchev): {{{ On Mon, Jul 21, 2008 at 4:20 AM, Mutt <[EMAIL PROTECTED]> wrote: > #2033: buffer overflow in attachment decoding function > > Comment (by pdmef): > > I can't reproduce a crash on debian and OS X with ti

Re: [Mutt] #2033: buffer overflow in attachment decoding function

#2033: buffer overflow in attachment decoding function Comment (by pdmef): I can't reproduce a crash on debian and OS X with tip. Can you retry with tip? I get the above valgrind errors, too but to me they seem to originate in glibc and not from mutt. -- Ticket URL:

Re: [Mutt] #2033: buffer overflow in attachment decoding function

#2033: buffer overflow in attachment decoding function Changes (by brendan): * milestone: => 1.6 -- Ticket URL:

Re: [Mutt] #2033: buffer overflow in attachment decoding function

#2033: buffer overflow in attachment decoding function Changes (by brendan): * priority: critical => major Old description: > {{{ > There is a potentially serious buffer overflow in > mutt-1.4.2/handler.c:mutt_decode_xbit() as well as the uuencode and other > attachment decoding functions, d