Wireshark-bugs: [Wireshark-bugs] [Bug 8559] New: Cannot read content of Ran Information Applicat
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 04 Apr 2013 08:04:36 +0000
Bug ID 8559
Summary Cannot read content of Ran Information Application Error Rim Container
Classification Unclassified
Product Wireshark
Version 1.8.6
Hardware x86-64
OS Ubuntu
Status UNCONFIRMED
Severity Major
Priority Low
Component Wireshark
Assignee bugzilla-admin@wireshark.org
Reporter l.wachowski@gmail.com 

Created attachment 10540 [details]
git patch

Build Information:
wireshark 1.8.6 (SVN Rev Unknown from unknown)

Copyright 1998-2013 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 (32-bit) with GTK+ 2.24.10, with Cairo 1.10.2, with Pango 1.30.0, with
GLib 2.32.3, with libpcap, with libz 1.2.3.4, without POSIX capabilities,
without SMI, without c-ares, without ADNS, without Lua, without Python, without
GnuTLS, without Gcrypt, without Kerberos, without GeoIP, without PortAudio,
with
AirPcap.

Running on Linux 3.2.0-39-generic-pae, with locale pl_PL.UTF-8, with libpcap
version 1.1.1, with libz 1.2.3.4, without AirPcap.

Built using gcc 4.6.3.

--
After import a proper payload with Ran-Information-Application-Error we can see
that "Missing Mandatory element (0x56) Application Error Container, rest of
dissection is suspect" in Application-Error-Rim-Container occurred, and payload
reading is stopped on field Rim-Pdu-Indications.

It is possible to reproduce this bug every time when we try to import proper
hex-stream with Ran-Information-Application-Error.

I saw this bug also on Windows 7.

I have attached file with proposal of my solution.
In file packet-bssgp.c in function de_bssgp_rim_pdu_indications is a switch
which handles the different behaviour of Rim-Pdu-Indication for different
messages. The last case is for Ran-Information-Error, and this is mistake.
Ran-Information-Error doesn't have field Rim-Pdu-Indication but
Ran-Information-Application-Error has it (comment in this case describes this
properly). Solution of this is just replace case
BSSGP_PDU_RAN_INFORMATION_ERROR to BSSGP_PDU_RAN_INFORMATION_APP_ERROR.

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