Wireshark-bugs: [Wireshark-bugs] [Bug 13092] New: Problem in decoding IMSI
Date: Fri, 04 Nov 2016 08:18:13 +0000
Bug ID 13092
Summary Problem in decoding IMSI
Product Wireshark
Version 2.2.1
Hardware x86-64
OS Windows 7
Status UNCONFIRMED
Severity Normal
Priority Low
Component Common utilities (libwsutil)
Assignee bugzilla-admin@wireshark.org
Reporter zheng.jiang@ericsson.com

Created attachment 15040 [details]
Screen shot of IMSI decode

Build Information:
Version 2.2.1 (v2.2.1-0-ga6fbd27 from master-2.2)

Copyright 1998-2016 Gerald Combs <gerald@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 (32-bit) with Qt 5.6.1, with WinPcap (4_1_3), with GLib 2.38.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, 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) i5-3427U CPU @ 1.80GHz (with SSE4.2), with 8055MB of
physical memory.


Built using Microsoft Visual C++ 12.0 build 40629

--
Hi, It seems there is one issue when encoding the ISMI number which is based on
North American.

The ISMI is: 311180000468028
MCC is 311, which is United State.

According to 3GPP 23.003: 
The MNC identifies the home PLMN of the mobile subscriber. The length of the
MNC (two or three digits) depends on the value of the MCC.

For North American, MNC length is 3. So the MNC should be 180 for this IMSI.
But the wireshark shows MNC is 18.

Is it a bug for wireshark to decode IMSI based on North America?

I attach the screen shot.


You are receiving this mail because:
  • You are watching all bug changes.