Table of Contents
Wireshark is the world's most popular network protocol analyzer. It is used for troubleshooting, analysis, development, and education.
The following vulnerabilities have been fixed. See the security advisory for details and a workaround.
On non-Windows systems, Wireshark could crash if the HOME environment variable contained sprintf-style string formatting characters. Discovered by babi. (Bug 3150)
Versions affected: 0.99.8 to 1.0.5
Wireshark could crash while reading a malformed NetScreen snoop file. Discovered by babi. (Bug 3151)
Versions affected: 0.99.7 to 1.0.5
Wireshark could crash while reading a Tektronix K12 text capture file. (Bug 1937)
Versions affected: 0.99.6 to 1.0.5
The following bugs have been fixed:
Crash when loading capture file and Preferences: NO Info column (Bug 2902)
Some Lua scripts may lead to corruption via out of bounds stack (Bug 3062)
Build with GLib 1.2 fails with error: 'G_MININT32' undeclared (Bug 3109)
Wrong decoding IMSI with GSM MAP protocol (Bug 3116)
Segmentation fault for "Follow TCP stream" (Bug 3119)
SMPP optional parameter 'network_error_code' incorrectly decoded (Bug 3128)
DHCPv6 dissector doesn't handle malformed FQDN (Bug 3134)
WCCP overrides CFLOW as decoded protocol (Bug 3175)
Improper decoding of MPLS echo reply IPv4 Interface and Label Stack Object (Bug 3179)
ANSI MAP fix for TRN digits/SMS and OTA subdissection (Bug 3214)
The 1.0 branch can now be built with Visual Studio 2008.
The version of GNUTLS included with the Windows packages has been updated from 2.3.8 to 2.6.3.
Wireshark source code and installation packages are available from the download page on the main web site.
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.
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.
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)
Capturing from named pipes might be delayed on Windows. (Bug 2200)
Filtering tshark captures with display filters (-R) no longer works. (Bug 2234)
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 and development services are available from CACE Technologies.
A complete FAQ is available on the Wireshark web site.