Wireshark-users: [Wireshark-users] Wireshark 2.2.16 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 18 Jul 2018 14:39:17 -0700
I'm proud to announce the release of Wireshark 2.2.16.
__________________________________________________________________
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:
* [1]wnpa-sec-2018-06
RPKI-Router infinite loop. [2]Bug 14414. [3]CVE-2018-7325.
* [4]wnpa-sec-2018-34
BGP dissector large loop. [5]Bug 13741. [6]CVE-2018-14342.
* [7]wnpa-sec-2018-35
ISMP dissector crash. [8]Bug 14672. [9]CVE-2018-14344.
* [10]wnpa-sec-2018-36
Multiple dissectors could crash. [11]Bug 14675. [12]CVE-2018-14340.
* [13]wnpa-sec-2018-37
ASN.1 BER dissector crash. [14]Bug 14682. [15]CVE-2018-14343.
* [16]wnpa-sec-2018-38
MMSE dissector infinite loop. [17]Bug 14738. [18]CVE-2018-14339.
* [19]wnpa-sec-2018-39
DICOM dissector crash. [20]Bug 14742. [21]CVE-2018-14341.
* [22]wnpa-sec-2018-40
Bazaar dissector infinite loop. [23]Bug 14841.
* [24]wnpa-sec-2018-41
HTTP2 dissector crash. [25]Bug 14869.
The following bugs have been fixed:
* ISMP.EDP "Tuples" dissected incorrectly. ([26]Bug 4943)
* Wireshark crashes when changing profiles. ([27]Bug 11648)
* randpkt can write packets that libwiretap can't read. ([28]Bug
14107)
* Crafted UDP packet causes large memory usage. ([29]Bug 14473)
* Error received from dissect_wccp2_hash_assignment_info(). ([30]Bug
14573)
* IP address to name resolution doesn't work in TShark. ([31]Bug
14711)
* proto_tree_add_protocol_format might leak memory. ([32]Bug 14719)
* DICOM dissector needs to check for packet offset overflow. ([33]Bug
14742)
* Formatting of OSI area addresses/address prefixes goes past the end
of the area address/address prefix. ([34]Bug 14744)
* ICMPv6 Router Renumbering - Packet Dissector - malformed. ([35]Bug
14755)
* WiMAX HARQ MAP decoder segfaults when length is too short. ([36]Bug
14780)
* HTTP PUT request following a HEAD request is not correctly decoded.
([37]Bug 14793)
* SYNC PDU type 3 miss the last PDU length. ([38]Bug 14823)
* Reversed 128 bits service UUIDs when Bluetooth Low Energy
advertisement data are dissected. ([39]Bug 14843)
* Issues with Wireshark when the user doesn't have permission to
capture. ([40]Bug 14847)
* Wrong description when LE Bluetooth Device Address type is
dissected. ([41]Bug 14866)
* LE Role advertisement type (0x1c) is not dissected properly
according to the Bluetooth specification. ([42]Bug 14868)
* Wireshark doesn't properly display (deliberately) invalid 220
responses from Postfix. ([43]Bug 14878)
* DCE/RPC not dissected when "reserved for use by implementations"
flag bits set. ([44]Bug 14942)
* There's no option to include column headings when printing packets
or exporting packet dissections with Qt Wireshark. ([45]Bug 14945)
* CMake is unable to find LUA libraries. ([46]Bug 14983)
New and Updated Features
There are no new features in this release.
New File Format Decoding Support
There are no new file formats in this release.
New Protocol Support
There are no new protocols in this release.
Updated Protocol Support
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
New and Updated Capture File Support
There is no new or updated capture file support in this release.
New and Updated Capture Interfaces support
There are no new or updated capture interfaces supported in this
release.
Major API Changes
There are no major API changes in this release.
__________________________________________________________________
Getting Wireshark
Wireshark source code and installation packages are available from
[47]https://www.wireshark.org/download.html.
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 [48]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
Dumpcap might not quit if Wireshark or TShark crashes. ([49]Bug 1419)
The BER dissector might infinitely loop. ([50]Bug 1516)
Capture filters aren't applied when capturing from named pipes.
([51]Bug 1814)
Filtering tshark captures with read filters (-R) no longer works.
([52]Bug 2234)
Application crash when changing real-time option. ([53]Bug 4035)
Wireshark and TShark will display incorrect delta times in some cases.
([54]Bug 4985)
Wireshark should let you work with multiple capture files. ([55]Bug
10488)
__________________________________________________________________
Getting Help
Community support is available on [56]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 [57]the web site.
Official Wireshark training and certification are available from
[58]Wireshark University.
__________________________________________________________________
Frequently Asked Questions
A complete FAQ is available on the [59]Wireshark web site.
__________________________________________________________________
Last updated 2018-07-18 20:55:02 UTC
References
1. https://www.wireshark.org/security/wnpa-sec-2018-06.html
2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14414
3. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7325
4. https://www.wireshark.org/security/wnpa-sec-2018-34.html
5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13741
6. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14342
7. https://www.wireshark.org/security/wnpa-sec-2018-35.html
8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14672
9. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14344
10. https://www.wireshark.org/security/wnpa-sec-2018-36.html
11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14675
12. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14340
13. https://www.wireshark.org/security/wnpa-sec-2018-37.html
14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14682
15. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14343
16. https://www.wireshark.org/security/wnpa-sec-2018-38.html
17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14738
18. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14339
19. https://www.wireshark.org/security/wnpa-sec-2018-39.html
20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14742
21. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14341
22. https://www.wireshark.org/security/wnpa-sec-2018-40.html
23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14841
24. https://www.wireshark.org/security/wnpa-sec-2018-41.html
25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14869
26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4943
27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11648
28. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14107
29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14473
30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14573
31. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14711
32. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14719
33. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14742
34. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14744
35. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14755
36. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14780
37. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14793
38. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14823
39. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14843
40. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14847
41. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14866
42. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14868
43. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14878
44. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14942
45. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14945
46. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14983
47. https://www.wireshark.org/download.html
48. https://www.wireshark.org/download.html#thirdparty
49. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
50. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
51. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
52. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
53. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
54. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
55. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
56. https://ask.wireshark.org/
57. https://www.wireshark.org/lists/
58. http://www.wiresharktraining.com/
59. https://www.wireshark.org/faq.html
Digests
wireshark-2.2.16.tar.bz2: 32552144 bytes
SHA256(wireshark-2.2.16.tar.bz2)=7dcc4e9f29ad8dd75849aa3b6f70b6ec82ab6899cb168096572775a6d97ced8a
RIPEMD160(wireshark-2.2.16.tar.bz2)=a7cf1bf879e3bc8e1a2aa261092e4ce439466d97
SHA1(wireshark-2.2.16.tar.bz2)=ac0c3b9dae966d530647c7a5927d1e8090284bde
Wireshark-win64-2.2.16.exe: 56194016 bytes
SHA256(Wireshark-win64-2.2.16.exe)=6532925f64557166ff450c21866fed5fca0f7f3513499cb93a162b004c9196c4
RIPEMD160(Wireshark-win64-2.2.16.exe)=aac1eb55cd6501cb375ffdc7f52e42b49a06945b
SHA1(Wireshark-win64-2.2.16.exe)=3bd30448d4c228d6f9c49eaa166f13f1170ca276
Wireshark-win32-2.2.16.exe: 44672040 bytes
SHA256(Wireshark-win32-2.2.16.exe)=b3352558ec597664f1a4e5c34de20f0880a8e84a67e47490f0b2f5726300e955
RIPEMD160(Wireshark-win32-2.2.16.exe)=7060577241b74be6b6a698764e44656e04eee9b5
SHA1(Wireshark-win32-2.2.16.exe)=3858e82489546cebacf5cca57b5e0f0316ec4f5a
WiresharkPortable_2.2.16.paf.exe: 46324128 bytes
SHA256(WiresharkPortable_2.2.16.paf.exe)=a95fe3f04553b803d2f444cbd6cf9744609e961ff0c12b41ce3165d6eef9857d
RIPEMD160(WiresharkPortable_2.2.16.paf.exe)=8205684d04d87010059e38845bebce008552d349
SHA1(WiresharkPortable_2.2.16.paf.exe)=d07ccbef79025a4711adcf1fb261162aa05c29f3
Wireshark 2.2.16 Intel 64.dmg: 40019313 bytes
SHA256(Wireshark 2.2.16 Intel
64.dmg)=cfd496a78395f4dd66c706ac99a8a00cc716cac3b60dfee2a07cd74e9b3ddcb2
RIPEMD160(Wireshark 2.2.16 Intel
64.dmg)=e6c80fefb313f9fd1f9ee3106124d7e1bf4e3b82
SHA1(Wireshark 2.2.16 Intel 64.dmg)=05307acf8e89735e5a8e9a13da0b7395ca01b7fc
You can validate these hashes using the following commands (among others):
Windows: certutil -hashfile Wireshark-win64-x.y.z.exe SHA256
Linux (GNU Coreutils): sha256sum wireshark-x.y.z.tar.xz
macOS: shasum -a 256 "Wireshark x.y.z Intel 64.dmg"
Other: openssl sha256 wireshark-x.y.z.tar.xz
Attachment:
signature.asc
Description: OpenPGP digital signature
- Prev by Date: [Wireshark-users] Wireshark 2.4.8 is now available
- Next by Date: Re: [Wireshark-users] packet dissection for documentation, bytes and tree
- Previous by thread: [Wireshark-users] Wireshark 2.4.8 is now available
- Next by thread: [Wireshark-users] ask.wireshark service unavailable
- Index(es):