Wireshark-users: [Wireshark-users] Wireshark 2.2.10 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Tue, 10 Oct 2017 12:45:05 -0700
I'm proud to announce the release of Wireshark 2.2.10.
__________________________________________________________________
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-2017-42
BT ATT dissector crash ([2]Bug 14049) [3]CVE-2017-15192
* [4]wnpa-sec-2017-43
MBIM dissector crash ([5]Bug 14056) [6]CVE-2017-15193
* [7]wnpa-sec-2017-44
DMP dissector crash ([8]Bug 14068) [9]CVE-2017-15191
The following bugs have been fixed:
* Wireshark crash when end capturing with "Update list of packets in
real-time" option off. ([10]Bug 13024)
* Diameter service response time statistics broken in 2.2.4. ([11]Bug
13442)
* Some Infiniband Connect Req fields are not decoded correctly.
([12]Bug 13997)
* wireshark-2.4.1/epan/dissectors/packet-dmp.c:1034: sanity check in
wrong place ?. ([13]Bug 14016)
* [oss-fuzz] ASAN: 232 byte(s) leaked in 4 allocation(s). ([14]Bug
14025)
* [oss-fuzz] ASAN: 47 byte(s) leaked in 1 allocation(s). ([15]Bug
14032)
* RTP Analysis "save as CSV" saves twice the forward stream, if two
streams are selected. ([16]Bug 14040)
* Cannot Apply Bitmask to Long Unsigned. ([17]Bug 14063)
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
BT ATT, DCERPC, DMP, E.212, H.248, InfiniBand, MBIM, RPC, 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
[18]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 [19]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. ([20]Bug 1419)
The BER dissector might infinitely loop. ([21]Bug 1516)
Capture filters aren't applied when capturing from named pipes.
([22]Bug 1814)
Filtering tshark captures with read filters (-R) no longer works.
([23]Bug 2234)
Application crash when changing real-time option. ([24]Bug 4035)
Wireshark and TShark will display incorrect delta times in some cases.
([25]Bug 4985)
Wireshark should let you work with multiple capture files. ([26]Bug
10488)
Dell Backup and Recovery (DBAR) makes many Windows applications crash,
including Wireshark. ([27]Bug 12036)
__________________________________________________________________
Getting Help
Community support is available on [28]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 [29]the web site.
Official Wireshark training and certification are available from
[30]Wireshark University.
__________________________________________________________________
Frequently Asked Questions
A complete FAQ is available on the [31]Wireshark web site.
__________________________________________________________________
Last updated 2017-10-10 19:28:42 UTC
References
1. https://www.wireshark.org/security/wnpa-sec-2017-42.html
2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14049
3. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15192
4. https://www.wireshark.org/security/wnpa-sec-2017-43.html
5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14056
6. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15193
7. https://www.wireshark.org/security/wnpa-sec-2017-44.html
8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14068
9. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15191
10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13024
11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13442
12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13997
13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14016
14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14025
15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14032
16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14040
17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14063
18. https://www.wireshark.org/download.html
19. https://www.wireshark.org/download.html#thirdparty
20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12036
28. https://ask.wireshark.org/
29. https://www.wireshark.org/lists/
30. http://www.wiresharktraining.com/
31. https://www.wireshark.org/faq.html
Digests
wireshark-2.2.10.tar.bz2: 32356703 bytes
SHA256(wireshark-2.2.10.tar.bz2)=8574a5e1fdec7affae640924bd46c1aed1bd866e02632fa5625e1450e4a50707
RIPEMD160(wireshark-2.2.10.tar.bz2)=a0164ae5e48de588bcc4df4f3c537dbf83b70cda
SHA1(wireshark-2.2.10.tar.bz2)=14ff541e84b43f5cff52fe44cdc1fbbcb8643dd2
Wireshark-win32-2.2.10.exe: 44654000 bytes
SHA256(Wireshark-win32-2.2.10.exe)=3aaa93ea069a014767b3058762fae4dee2424446bfdd1c258055178c37f035cf
RIPEMD160(Wireshark-win32-2.2.10.exe)=beb9a48646133a2e928bbf523527e811ec82e9f6
SHA1(Wireshark-win32-2.2.10.exe)=02943ecdfbc99217ded0b96678f9497ccf6b533b
Wireshark-win64-2.2.10.exe: 56147416 bytes
SHA256(Wireshark-win64-2.2.10.exe)=274568074742704a537b0ffb6435cf62c0a215a18c5b25cabdf10d19773a06a5
RIPEMD160(Wireshark-win64-2.2.10.exe)=6854b79770c655e8c8b2e6a931bad1a718427a4d
SHA1(Wireshark-win64-2.2.10.exe)=1343f45cd5ca39045373e0b9fb29f2ead4500b5a
WiresharkPortable_2.2.10.paf.exe: 46243952 bytes
SHA256(WiresharkPortable_2.2.10.paf.exe)=9d6667e79c4c102a20c213bb4dc7fb294d8b049b6c002b9ff622f9d5369fd67a
RIPEMD160(WiresharkPortable_2.2.10.paf.exe)=268b4ea127ebc684852d38e83e1c74e637c7c9ac
SHA1(WiresharkPortable_2.2.10.paf.exe)=5fe628b8bc32ea38f27c205ae9e61bf4fb60df07
Wireshark 2.2.10 Intel 64.dmg: 33507023 bytes
SHA256(Wireshark 2.2.10 Intel
64.dmg)=5696a29128a0a1e62b8a99132e74b5a60f1b6cbb37ab93c6591e74b0b53bdd1b
RIPEMD160(Wireshark 2.2.10 Intel
64.dmg)=9507440c53d1810cdd26754e4bedaab835f8370e
SHA1(Wireshark 2.2.10 Intel 64.dmg)=588da6d84e77cf736b457641306ffd9be47be123
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.2 is now available
- Next by Date: [Wireshark-users] Get expert info from tshark
- Previous by thread: [Wireshark-users] Wireshark 2.4.2 is now available
- Next by thread: [Wireshark-users] Get expert info from tshark
- Index(es):