Wireshark-bugs: [Wireshark-bugs] [Bug 7476] New: UMA dissector incorrectly passes MAC addresses

Date: Fri, 13 Jul 2012 09:47:12 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7476

           Summary: UMA dissector incorrectly passes MAC addresses to
                    wireshark core
           Product: Wireshark
           Version: SVN
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Dissection engine (libwireshark)
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: laforge@xxxxxxxxxxxx


Created attachment 8772
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=8772
patch to fix the issue

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

Copyright 1998-2012 Gerald Combs <gerald@xxxxxxxxxxxxx> 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.10, with Cairo 1.12.2, with Pango 1.30.0, with
GLib 2.32.3, with libpcap, with libz 1.2.7, with POSIX capabilities (Linux),
with libnl 1, without SMI, without c-ares, with ADNS, without Lua, without
Python, with GnuTLS 2.12.20, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
with PortAudio <= V18, without AirPcap.

Running on Linux 3.2.0-2-amd64, with locale en_US.UTF-8, with libpcap version
1.3.0, with libz 1.2.7, GnuTLS 2.12.20, Gcrypt 1.5.0.

Built using gcc 4.7.1.

BUT: I've seen this even with much older versions (e.g. 1.7.x)
--
When dissecting an UMA capture, the UMA dissector causes an error in proto.c,
line 1346.  The reason is that it passes a MAC address (6 byte) with a length
field of 7 byte.  In proto.c it is checked if the 7 == 6 and thus aborted.

I'm attaching a patch against current SVN to fix this.  I'll also provide a
pcap file to illustrate the problem.

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