Date: Mon, 31 Mar 2003 14:04:46 -0600 From: "Jacques A. Vidrine" <nectar@FreeBSD.org> To: Brett Glass <brett@lariat.org> Cc: freebsd-security@FreeBSD.org Subject: Re: what was that? Message-ID: <20030331200446.GA41695@madman.celabo.org> In-Reply-To: <4.3.2.7.2.20030331122909.031ac940@localhost> <4.3.2.7.2.20030331122450.031ace50@localhost> References: <4.3.2.7.2.20030331122909.031ac940@localhost> <4.3.2.7.2.20030331102232.0327fa90@localhost> <3E887850.7010100@drweb.ru> <4.3.2.7.2.20030331102232.0327fa90@localhost> <4.3.2.7.2.20030331122450.031ace50@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 31, 2003 at 12:26:56PM -0700, Brett Glass wrote: > >No, I don't think so. > > You have a right to disagree, of course. However, some MUAs > HAVE been reported to have buffer overflow vulnerabilities > that can be exploited via an excessively long message ID > header. I have installed a filter that shortens them to > prevent Outlook users from being nailed by this bug. On Mon, Mar 31, 2003 at 12:29:59PM -0700, Brett Glass wrote: > Oh, and elm apparently has a buffer overflow in Message-ID header > handling too. See > > http://www.linuxsecurity.com/advisories/redhat_advisory-1497.html Read my post about the type of data that was in the Message-ID. It doesn't /look/ like an overflow --- I did not recognize the data as executable code `as is', nor once it was decoded. Thus, I do not believe that it is a particular attempt at causing a buffer overflow in a MTA or MUA. Cheers, -- Jacques A. Vidrine <nectar@celabo.org> http://www.celabo.org/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos jvidrine@verio.net . nectar@FreeBSD.org . nectar@kth.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030331200446.GA41695>