ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 6235] BACnet context tags greater than 14 give [Malformed

Date: Wed, 31 Aug 2011 10:55:47 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6235

Lori Tribble <ljtconsulting@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ljtconsulting@xxxxxxxxx

--- Comment #1 from Lori Tribble <ljtconsulting@xxxxxxxxx> 2011-08-31 10:55:45 PDT ---
I looked into this and have found the issue is not with decoding the context
tag itself but with the recovery of not handling a tag type in our switch
statements.  We resort to doing nothing but we have already incremented the
offset by our tag size amount.  The standard way to break out of the loops is
to see if lastoffset == offset.  In this case it will not so we keep going even
though we didn't process.  I think the default statement needs to skip the
whole context.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.