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:
RPKI-Router infinite loop. Bug 14414. CVE-2018-7325.
BGP dissector large loop. Bug 13741. CVE-2018-14342.
ISMP dissector crash. Bug 14672. CVE-2018-14344.
Multiple dissectors could crash. Bug 14675. CVE-2018-14340.
ASN.1 BER dissector crash. Bug 14682. CVE-2018-14343.
MMSE dissector infinite loop. Bug 14738. CVE-2018-14339.
DICOM dissector crash. Bug 14742. CVE-2018-14341.
Bazaar dissector infinite loop. Bug 14841.
HTTP2 dissector crash. Bug 14869.
The following bugs have been fixed:
- ISMP.EDP "Tuples" dissected incorrectly. (Bug 4943)
- Wireshark crashes when changing profiles. (Bug 11648)
- randpkt can write packets that libwiretap can’t read. (Bug 14107)
- Crafted UDP packet causes large memory usage. (Bug 14473)
- Error received from dissect_wccp2_hash_assignment_info(). (Bug 14573)
- IP address to name resolution doesn’t work in TShark. (Bug 14711)
- proto_tree_add_protocol_format might leak memory. (Bug 14719)
- DICOM dissector needs to check for packet offset overflow. (Bug 14742)
- Formatting of OSI area addresses/address prefixes goes past the end of the area address/address prefix. (Bug 14744)
- ICMPv6 Router Renumbering - Packet Dissector - malformed. (Bug 14755)
- WiMAX HARQ MAP decoder segfaults when length is too short. (Bug 14780)
- HTTP PUT request following a HEAD request is not correctly decoded. (Bug 14793)
- SYNC PDU type 3 miss the last PDU length. (Bug 14823)
- Reversed 128 bits service UUIDs when Bluetooth Low Energy advertisement data are dissected. (Bug 14843)
- Issues with Wireshark when the user doesn’t have permission to capture. (Bug 14847)
- Wrong description when LE Bluetooth Device Address type is dissected. (Bug 14866)
- LE Role advertisement type (0x1c) is not dissected properly according to the Bluetooth specification. (Bug 14868)
- Wireshark doesn’t properly display (deliberately) invalid 220 responses from Postfix. (Bug 14878)
- DCE/RPC not dissected when "reserved for use by implementations" flag bits set. (Bug 14942)
- There’s no option to include column headings when printing packets or exporting packet dissections with Qt Wireshark. (Bug 14945)
- CMake is unable to find LUA libraries. (Bug 14983)
ASN.1 BER, Bazaar, BGP, Bluetooth, Bluetooth HCI_CMD, CIGI, DCERPC, DICOM, GSM A GM, HTTP, HTTP2, IAX2, ICMPv6, IEEE 802.11, ISMP, LISP, MMSE, MTP3, PPI GPS, Q.931, RPKI-Router, SMTP, STUN, SYNC, T.30, WAP, WCCP, WiMax HARQ Map Message, and WSP
There is no new or updated capture file support in this release.
There are no new or updated capture interfaces supported in this release.
Wireshark source code and installation packages are available from https://www.wireshark.org/download.html.
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.
Dumpcap might not quit if Wireshark or TShark crashes. (Bug 1419)
The BER dissector might infinitely loop. (Bug 1516)
Capture filters aren’t applied when capturing from named pipes. (Bug 1814)
Filtering tshark captures with read filters (-R) no longer works. (Bug 2234)
Application crash when changing real-time option. (Bug 4035)
Wireshark and TShark will display incorrect delta times in some cases. (Bug 4985)
Wireshark should let you work with multiple capture files. (Bug 10488)
Community support is available on Wireshark’s Q&A site and on the wireshark-users mailing list. Subscription information and archives for all of Wireshark’s mailing lists can be found on the web site.
Official Wireshark training and certification are available from Wireshark University.
A complete FAQ is available on the Wireshark web site.