Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • wireshark wireshark
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,341
    • Issues 1,341
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 153
    • Merge requests 153
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Wireshark Foundation
  • wiresharkwireshark
  • Issues
  • #17667
Closed
Open
Created Oct 19, 2021 by Suhas Bindinganavale Ramadas@suhasbr

Wireshark is unable to decode the IMSI IE received in BSSMAP Perform Location request

Summary

Wireshark is unable to decode the IMSI IE received in BSSMAP Perform Location request

Steps to reproduce

Hex dump of PL request message 00312b44010005080024f22007d099d5130b601404e2801001200100004801304301003e040100000000083920840000023099

What is the current bug behavior?

As per 49.031, IMSI tag is 00 but wireshark fails to decode 00. Instead considers 08 as valid message type

Section 10.2 Information Element Identifiers The next list shows the coding of the Information Element Identifiers used in the present document.

0 0 0 0 0 0 0 0 IMSI 10.11

What is the expected correct behavior?

As per my understanding, 00 is the valid message type for IMSI.

Sample capture fileplreq-imsi.pcap

pcap traces attached for reference

Relevant logs and/or screenshots

image

Build information

(In Wireshark, select Help->About Wireshark from the main menu and use the button "Copy To Clipboard". Please paste the complete output here. Or from the command line, run `tshark -v` or `wireshark -v`)

3.4.9 (v3.4.9-0-g365e236f5efe)

Compiled (64-bit) with Qt 5.15.2, with libpcap, with GLib 2.52.3, with zlib
1.2.11, with SMI 0.4.8, with c-ares 1.15.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.39.2, with brotli, with LZ4, with Zstandard, with
Snappy, with libxml2 2.9.9, with QtMultimedia, with automatic updates using
WinSparkle 0.5.7, with AirPcap, with SpeexDSP (using bundled resampler), with
Minizip.

Running on 64-bit Windows 10 (1909), build 18363, with Intel(R) Core(TM)
i5-8265U CPU @ 1.60GHz (with SSE4.2), with 16190 MB of physical memory, with
locale English_United States.utf8, with light display mode, without HiDPI, with
Npcap version 1.31, based on libpcap version 1.10.1-PRE-GIT, with GnuTLS 3.6.3,
with Gcrypt 1.8.3, with brotli 1.0.2, without AirPcap, binary plugins supported
(21 loaded).

Built using Microsoft Visual Studio 2019 (VC++ 14.29, build 30040).

[plreq-imsi.pcap](/uploads/d6c473603ee5a60b5f7da50568bcf6d9/plreq-imsi.pcap)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking