Your message dated Tue, 16 Sep 2025 11:18:54 +0000
with message-id <[email protected]>
and subject line Bug#1114559: Removed package(s) from unstable
has caused the Debian Bug report #844719,
regarding Out of bounds read when using a malformated pcap file
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
844719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844719
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tcptrace
Version: 6.6.7-4.1
Severity: normal
File: /usr/bin/tcptrace

Dear Maintainer,

   * What led up to the situation?
While developing a new fuzzer we discovered this bug.

   * What outcome did you expect instead?
We expected the program not to crash. I'm attaching an input file that
triggers this bug. The bug can be triggered on x86_64 as well.

Here's a stack trace:
"""
Ostermann's tcptrace -- version 6.6.7 -- Thu Nov  4, 2004

TCP packet 10: reserved bits are not all zero.
        Further warnings disabled, use '-w' for more info

Program received signal SIGSEGV, Segmentation fault.
0x08058ecc in MemCpy (vp1=0x80caab0, vp2=0x80baab6, n=4294699681) at
tcptrace.c:2620
2620            *p1++=*p2++;
(gdb) bt
#0  0x08058ecc in MemCpy (vp1=0x80caab0, vp2=0x80baab6, n=4294699681) at
tcptrace.c:2620
#1  0x080558c4 in callback (user=0x0, phdr=0xbffff1bc, buf=0x80baaa8 "")
at tcpdump.c:166
#2  0xb7f4ba18 in pcap_offline_read (p=0x80ba8a0, cnt=1,
callback=0x8055850 <callback>,
    user=0x0) at ./savefile.c:404
#3  0xb7f3c8f6 in pcap_dispatch (p=0x80ba8a0, cnt=1, callback=0x8055850
<callback>,
    user=0x0) at ./pcap.c:829
#4  0x080556d8 in pread_tcpdump (ptime=0x80a75c8 <current_time>,
plen=0xbffff29c,
    ptlen=0xbffff2a0, pphys=0xbffff298, pphystype=0xbffff294,
ppip=0xbffff28c,
    pplast=0xbffff2a4) at tcpdump.c:247
#5  0x08058098 in ProcessFile (filename=0x80caab0 "E`") at tcptrace.c:966
#6  0x08049fba in main (argc=1, argv=0xbffff4f4) at tcptrace.c:785
"""


-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tcptrace depends on:
ii  libc6       2.19-18+deb8u4
ii  libpcap0.8  1.6.2-2

Versions of packages tcptrace recommends:
ii  tcpdump          4.6.2-5+deb8u1
ii  xplot-xplot.org  0.90.7.1-2

tcptrace suggests no packages.

-- debconf-show failed

Attachment: tcptrace-2016-05-18T02-38-38.155527.pcap
Description: tcptrace-2016-05-18T02-38-38.155527.pcap

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Version: 6.6.7-6+rm

Dear submitter,

as the package tcptrace has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1114559

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to