Your message dated Sat, 04 Nov 2006 07:18:36 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#395248: fixed in ngrep 1.44-3
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: ngrep
Version: 1.44-2
Severity: important
Tags: security

   ngrep's signal handler, clean_exit(), calls free() and other cleanup
functions in a non-idempotent way. There is an easy way to trigger the
bug by running "ngrep . | cat", then pressing Ctrl-C. ngrep will get a
SIGINT signal from the shell, and a SIGPIPE signal from the dying cat
process, resulting in clean_exit() being called twice.

   Adding some code like this at the beginning of clean_exit() probably
fixes the issue:

    static volatile int cleaned = 0;
    if(cleaned++) exit(sig);

   This is probably a security issue, too, because the data ngrep is
handling comes from the network, but it does not seem to be easily
exploitable (famous last words, I know). Feel free to remove the
security tag if you disagree, but a process running as root dumping
core does not seem right to me in any case.

   Also the argument for clean_exit seems wrong to me, signal(2) says
int, not int32_t.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.11
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages ngrep depends on:
ii  libc6                        2.3.6.ds1-6 GNU C Library: Shared libraries
ii  libpcap0.8                   0.9.5-1     System interface for user-level pa
ii  libpcre3                     6.7-1       Perl 5 Compatible Regular Expressi

ngrep recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: ngrep
Source-Version: 1.44-3

We believe that the bug you reported is fixed in the latest version of
ngrep, which is due to be installed in the Debian FTP archive:

ngrep_1.44-3.diff.gz
  to pool/main/n/ngrep/ngrep_1.44-3.diff.gz
ngrep_1.44-3.dsc
  to pool/main/n/ngrep/ngrep_1.44-3.dsc
ngrep_1.44-3_i386.deb
  to pool/main/n/ngrep/ngrep_1.44-3_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Romain Francoise <[EMAIL PROTECTED]> (supplier of updated ngrep package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat,  4 Nov 2006 15:54:58 +0100
Source: ngrep
Binary: ngrep
Architecture: source i386
Version: 1.44-3
Distribution: unstable
Urgency: low
Maintainer: Romain Francoise <[EMAIL PROTECTED]>
Changed-By: Romain Francoise <[EMAIL PROTECTED]>
Description: 
 ngrep      - grep for network traffic
Closes: 395248
Changes: 
 ngrep (1.44-3) unstable; urgency=low
 .
   * Backport patch from upstream CVS making the `clean_exit' signal
     handler safer (closes: #395248).
Files: 
 d9f6924383640973be270143bf19dcb3 603 net optional ngrep_1.44-3.dsc
 4d7941b9c58d83bd0424f1ae8005a566 10819 net optional ngrep_1.44-3.diff.gz
 c84f660b3cf3b619b7191d809ded9ddd 29668 net optional ngrep_1.44-3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFTKpqogN2vsA8Vt8RAmjsAJ9UwWIaMgoFQMw7cmdfwNJwGSIQdQCgo2Uo
s0FgBDFk95T4i4pdaqd2+ao=
=nRh6
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to