Join us June 15-20 for SharkFest'24 US, the official Wireshark Developer & User Conference

Wireshark 1.2.1 Release Notes

What is Wireshark?

Wireshark is the world's most popular network protocol analyzer. It is used for troubleshooting, analysis, development, and education.

What's New

Bug Fixes

The following vulnerabilities have been fixed. See the security advisory for details and a workaround.

  • The IPMI dissector could overrun a buffer.

    Versions affected: 1.2.0

  • The AFS dissector could crash.

    Versions affected: 0.9.2 to 1.2.0

  • The Infiniband dissector could crash on some platforms.

    Versions affected: 1.0.6 to 1.2.0

  • The Bluetooth L2CAP dissector could crash.

    Versions affected: 1.2.0

  • The RADIUS dissector could crash.

    Versions affected: 1.2.0

  • The MIOP dissector could crash.

    Versions affected: 1.2.0

  • The sFlow dissector could use excessive CPU and memory.

    Versions affected: 1.2.0

The following bugs have been fixed:

  • Wireshark could crash while reading a pcap-ng file.

  • Wireshark could crash while reading a PacketLogger file.

  • CFLOW decoding is wrong for IPv6 fields (Bug 3328)

  • Buildbot crash output: fuzz-2009-04-24-2891.pcap (Bug 3438)

  • packet-dcm, corrupt DICOM export files (Bug 3493)

  • GeoIP map should use random temporary file name (Bug 3530)

  • Wireshark crashes when range_string is the data type (Bug 3536)

  • Pcap-ng breaks VoIP call data (Bug 3539)

  • ANSI MAP legInformation BER Error (Bug 3541)

  • Starting Wireshark Portable 1.2.0 gives error message. (Bug 3547)

  • On Windows, Wireshark could crash on startup. (Bug 3555)

  • The title in the TCP sequence graphs is too short. (Bug 3556)

  • USB Packets in pcap-ng Files Not Dissected Properly (Bug 3560)

  • 802.11 decryption is broken (Bug 3590)

  • SMB2 Error Response doesn't decode properly (Bug 3609)

  • uses deprecated autoconf test for gnutls detection (Bug 3627)

  • Radius Malformed Packet error message (Bug 3635)

  • Wireshark could crash when loading a profile. (Bug 3640)

  • Analyze->Decode as... menu item becomes unavailable (Bug 3642)

  • btsnoop: Incorrect error message for not supported datalink type (Bug 3645)

  • Decode error for network-id in BICC BCU-ID (Bug 3648)

  • IEC 60870-5-104 dissector decodes nothing (Bug 3650)

  • radius_register_avp_dissector() can stop RADIUS dissector from working correctly (Bug 3651)

  • ANSI ISUP Cause indicators with coding standard=ANSI fail to dissect. (Bug 3654)

  • Wrong field position in PacketCable Multimedia Extended Classifier (Bug 3656)

  • FF Protocol "FMS Initiate - Version OD Calling" field packet data not unpacked properly (Bug 3694)

  • hci_h4: Optimize column/field handling (Bug 3703)

  • BSSLAP Protocol Not Decoded In BSSMAP-LE Messages (Bug 3711)

  • Description of tshark -t dd missing from tshark.pod (Bug 3723)

  • Problem in packet-per.c for ASN.1 PER Encoding (Bug 3733)

  • [SNMP] Crash when dissecting packet (custom MIB) (Bug 3746)

New and Updated Features

There are no new or updated features in this release.

New Protocol Support

There are no new protocols in this release.

Updated Protocol Support

AFS, ANSI ISUP, ANSI MAP, ASN.1 PER, Bluetooth HCI H4, Bluetooth L2CAP, BSS CFLOW, COPS, Diameter, DICOM, FF-HSE, ICMPv6, IEC-60870-5-104, IEEE 802.11, Infiniband, IPMI, MIOP, RADIUS, RSVP, sFlow, SNMP, SMB2, ZIOP

New Capture File Support

Btsnoop, DCT3, Packetlogger, pcap-ng.

Getting Wireshark

Wireshark source code and installation packages are available from the download page on the main web site.

Vendor-supplied Packages

Most Linux and Unix vendors supply their own Wireshark packages. You can usually install or upgrade Wireshark using the package management system specific to that platform. A list of third-party packages can be found on the download page on the Wireshark web site.

File Locations

Wireshark and TShark look in several different locations for preference files, plugins, SNMP MIBS, and RADIUS dictionaries. These locations vary from platform to platform. You can use About->Folders to find the default locations on your system.

Known Problems

Wireshark may appear offscreen on multi-monitor Windows systems. (Bug 553)

Wireshark might make your system disassociate from a wireless network on OS X. (Bug 1315)

Dumpcap might not quit if Wireshark or TShark crashes. (Bug 1419)

The BER dissector might infinitely loop. (Bug 1516)

Wireshark can't dynamically update the packet list. This means that host name resolutions above a certain response time threshold won't show up in the packet list. (Bug 1605)

Capture filters aren't applied when capturing from named pipes. (Bug 1814)

Wireshark might freeze when reading from a pipe. (Bug 2082)

Filtering tshark captures with display filters (-R) no longer works. (Bug 2234)

The 64-bit Windows installer does not ship with the same libraries as the 32-bit installer.

Getting Help

Community support is available on the wireshark-users mailing list. Subscription information and archives for all of Wireshark's mailing lists can be found on the web site.

Commercial support, training, and development services are available from CACE Technologies.

Frequently Asked Questions

A complete FAQ is available on the Wireshark web site.