| Bug ID |
12557
|
| Summary |
Statistics->Endpoints window column auto-size is broken when displayed records is >= 1000
|
| Product |
Wireshark
|
| Version |
2.1.x (Experimental)
|
| Hardware |
x86-64
|
| OS |
Windows Server 2008
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 2.1.0-git (v2.1.0rc0-2960-gcb2627c from master)
Compiled (64-bit) with GTK+ 2.24.23, with Cairo 1.12.16, with Pango 1.36.8,
with
WinPcap (4_1_3), with GLib 2.42.0, with zlib 1.2.8, with SMI 0.4.8, with c-ares
1.11.0, with Lua 5.2, with GnuTLS 3.2.15, with Gcrypt 1.6.2, with MIT Kerberos,
with GeoIP, with PortAudio V19-devel (built May 9 2016), with AirPcap.
Running on 64-bit Windows Server 2008 Service Pack 2, build 6002, with locale
English_United States.1252, with WinPcap version 4.1.3 (packet.dll version
4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with
GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (with SSE4.2), with 6133MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 40629
--
With 64-bit wireshark-gtk.exe the Statistics->Endpoints window column auto-size
goes bonkers and sets wildly incorrect column widths once the number of
displayed rows exceeds, precisely, 999 entries.
This applies to all the tabs, especially Ethernet, IPv4 and TCP.
Is true with Maxmind GeoIP active and inactive.
-----
A guess is that an array related to column autosizing somewhere was set to 1000
lines long ago when that seemed a ridiculously large number of endpoints.
Possibly this could pose a security vulnerability due to a table overflow.
You are receiving this mail because:
- You are watching all bug changes.
