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.
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
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
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
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
5 matches
Mail list logo