Wireshark-bugs: [Wireshark-bugs] [Bug 10522] New: GSM MAP LocationNumber parameter decoded incor
Date: Wed, 01 Oct 2014 22:29:36 +0000
Bug ID 10522
Summary GSM MAP LocationNumber parameter decoded incorrectly
Product Wireshark
Version 1.12.1
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Minor
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter geoffreyhart@sympatico.ca

Created attachment 13116 [details]
Sample packet capture

Build Information:
Version 1.12.1 (v1.12.1-0-g01b65bf from master-1.12)

Copyright 1998-2014 Gerald Combs <gerald@wireshark.org> and contributors.
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 GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.1.22, with Gcrypt 1.6.0,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Sep 16 2014),
with
AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.1.22, Gcrypt 1.6.0, without AirPcap.
Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz, with 32707MB of physical memory.


Built using Microsoft Visual C++ 10.0 build 40219

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Parameter LocationNumber in GSM MAP message ProvideSubscriberInfo is decoded
incorrectly.

In the attached sample packet, the LocationNumber field re-uses the same bytes
used in the header (Odd/even, Nature of Address, INN, Numbering Plan, Address
Presentation Restricted, Screening Indicator) again in the Address Digits and
Country code; leading to 2 extra bytes being pre-pended incorrectly onto this
field.

Correct decode is documented in ITU-T Q.763 (12/1999)


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