Bug#226356: Buffer overflow vulnerability (CAN-2003-0850)

2004-01-07 Thread Colin Watson
On Mon, Jan 05, 2004 at 06:17:07PM -0800, Matt Zimmerman wrote: Package: libnids Severity: grave The TCP reassembly functionality in libnids before 1.18 allows remote attackers to cause memory corruption and possibly execute arbitrary code via overlarge TCP packets.

Bug#226553: emelfm: implicitly declared function returns a pointer that is used

2004-01-07 Thread lamont
Package: emelfm Version: 0.9.2-6 Severity: important The following functions are used in your pacakge without being defined (you probably forgot a header file) in your package, and the return value is converted to a pointer. This is guaranteed to be fatal on ia64, and probably any 64-bit

Bug#226650: wn: implicitly declared function returns a pointer that is used

2004-01-07 Thread lamont
Package: wn Version: 2.2.9-3 Severity: important The following functions are used in your pacakge without being defined (you probably forgot a header file) in your package, and the return value is converted to a pointer. This is guaranteed to be fatal on ia64, and probably any 64-bit

Bug#226356: Buffer overflow vulnerability (CAN-2003-0850)

2004-01-07 Thread Colin Watson
On Tue, Jan 06, 2004 at 11:22:55AM +, Steve Kemp wrote: On Mon, Jan 05, 2004 at 06:17:07PM -0800, Matt Zimmerman wrote: Package: libnids Severity: grave The TCP reassembly functionality in libnids before 1.18 allows remote attackers to cause memory corruption and possibly execute

Bug#226356: marked as done (Buffer overflow vulnerability (CAN-2003-0850))

2004-01-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Jan 2004 16:39:47 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#226356: fixed in libnids 1.18-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your