https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15685
Bug ID: 15685
Summary: Wireshark does not respond (circle of death) when SMPP
data is sent on port 6000
Product: Wireshark
Version: 3.0.0
Hardware: x86-64
OS: Windows Server 2016
Status: UNCONFIRMED
Severity: Major
Priority: Low
Component: Dissection engine (libwireshark)
Assignee: bugzilla-ad...@wireshark.org
Reporter: buch...@gmail.com
Target Milestone: ---
Build Information:
Version 3.0.0 (v3.0.0-0-g937e33de)
Copyright 1998-2019 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html> This is free software;
see the source for copying conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with Qt 5.12.1, with WinPcap SDK (WpdPack) 4.1.2, with GLib
2.52.2, with zlib 1.2.11, with SMI 0.4.8, with c-ares 1.14.0, with Lua 5.2.4,
with GnuTLS 3.6.3 and PKCS #11 support, with Gcrypt 1.8.3, with MIT Kerberos,
with MaxMind DB resolver, with nghttp2 1.14.0, with LZ4, with Snappy, with
libxml2 2.9.9, with QtMultimedia, with AirPcap, with SBC, with SpanDSP, with
bcg729.
Running on 64-bit Windows Server 2016 (1607), build 14393, with Intel(R)
Xeon(R) CPU E5-2630 v2 @ 2.60GHz (with SSE4.2), with 8189 MB of physical
memory, with locale English_Australia.1252, with Npcap version 0.99-r9, based
on libpcap version 1.8.1, with GnuTLS 3.6.3, with Gcrypt 1.8.3, without
AirPcap, binary plugins supported (14 loaded). Built using Microsoft Visual
Studio 2017 (VC++ 14.12, build 25835).
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
We have a SMPP service provider who uses port 6000 for SMPP protocol. We run a
capture and observe SMPP binds and enquire links no problems. However, when
our SMPP Client application sends data (Submit_SM) to the smpp service
provider, wireshark hangs.
We reproduced this on previous releases of wireshark 2.4 2.6 etc.
We also reproduced this on another VM running windows 2012 R2.
We believe therefore, that the issue is with wireshark.
We observed wireshark CPU activity while the circle of death was happening, our
SMPP data actually got to the service provider but wireshark did not respond
and therefore could not display any packets on the screen after we sent data on
port 6000.
We set the decode-as option to dissect port 6000 as SMPP protocol.
hope you can reproduce this.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
