| Bug ID |
10832
|
| Summary |
SIGSEGV in g_strlcpy
|
| Product |
Wireshark
|
| Version |
1.12.2
|
| Hardware |
x86
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Capture file support (libwiretap)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 13367 [details]
backtrace
Build Information:
wireshark 1.12.2 (Git Rev Unknown from unknown)
Compiled (64-bit) with GTK+ 3.14.6, with Cairo 1.14.0, with Pango 1.36.8, with
GLib 2.42.1, with libpcap, with libz 1.2.8, with POSIX capabilities (Linux),
with libnl 3, with SMI 0.4.8, without c-ares, without ADNS, with Lua 5.2,
without Python, with GnuTLS 3.3.11, with Gcrypt 1.6.2, with MIT Kerberos, with
GeoIP, with PortAudio V19-devel (built Jan 31 2014 21:19:35), without AirPcap.
Running on Linux 3.17.6-1-kdump, with locale de_DE.utf8, with libpcap version
1.6.2, with libz 1.2.8, GnuTLS 3.3.11, Gcrypt 1.6.2.
Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz
Built using gcc 4.9.2 20141224 (prerelease).
--
I'm trying to read a 60 MB pcap file, when after fully reading the file, during
disection, Wireshark will trigger a SIGSGV in g_strlcpy.
Backtrace is attached.
The pcap was collected on one of our gateways (Freifunk) and may contain
sensitive information about our users. Therefore I cannot upload it.
You are receiving this mail because:
- You are watching all bug changes.