Wireshark-users: [Wireshark-users] Wireshark 2.0.13 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Thu, 1 Jun 2017 13:45:04 -0700
I'm proud to announce the release of Wireshark 2.0.13.
__________________________________________________________________
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-22
Bazaar dissector infinite loop ([2]Bug 13599) [3]CVE-2017-9352
* [4]wnpa-sec-2017-24
DHCP dissector read overflow ([5]Bug 13609, [6]Bug 13628)
[7]CVE-2017-9351
* [8]wnpa-sec-2017-25
SoulSeek dissector infinite loop ([9]Bug 13631) [10]CVE-2017-9346
* [11]wnpa-sec-2017-26
DNS dissector infinite loop ([12]Bug 13633) [13]CVE-2017-9345
* [14]wnpa-sec-2017-27
DICOM dissector infinite loop ([15]Bug 13685) [16]CVE-2017-9349
* [17]wnpa-sec-2017-28
openSAFETY dissector memory exhaustion ([18]Bug 13649)
[19]CVE-2017-9350
* [20]wnpa-sec-2017-29
BT L2CAP dissector divide by zero ([21]Bug 13701) [22]CVE-2017-9344
* [23]wnpa-sec-2017-30
MSNIP dissector crash ([24]Bug 13725) [25]CVE-2017-9343
* [26]wnpa-sec-2017-32
RGMP dissector crash ([27]Bug 13646) [28]CVE-2017-9354
The following bugs have been fixed:
* DICOM dissection error. ([29]Bug 13164)
* Can not export captured DICOM objects in version 2.2.5. ([30]Bug
13570)
* LibFuzzer: ISUP dissector bug (isup.number_different_meaning).
([31]Bug 13588)
* Dissector Bug, protocol BT ATT. ([32]Bug 13590)
* [oss-fuzz] UBSAN: shift exponent 105 is too large for 32-bit type
int in packet-ositp.c:551:79. ([33]Bug 13606)
* [oss-fuzz] UBSAN: shift exponent -77 is negative in
packet-netflow.c:7717:23. ([34]Bug 13607)
* [oss-fuzz] UBSAN: shift exponent 1959 is too large for 32-bit type
int in packet-sigcomp.c:2128:28. ([35]Bug 13610)
* [oss-fuzz] UBSAN: shift exponent 63 is too large for 32-bit type
guint32 (aka unsigned int) in packet-rtcp.c:917:24. ([36]Bug 13611)
* [oss-fuzz] UBSAN: shift exponent 70 is too large for 64-bit type
guint64 (aka unsigned long) in dwarf.c:42:43. ([37]Bug 13616)
* [oss-fuzz] UBSAN: shift exponent 32 is too large for 32-bit type
int in packet-xot.c:260:23. ([38]Bug 13618)
* [oss-fuzz] UBSAN: shift exponent -5 is negative in
packet-sigcomp.c:1722:36. ([39]Bug 13619)
* [oss-fuzz] UBSAN: index 2049 out of bounds for type char [2049] in
packet-quakeworld.c:134:5. ([40]Bug 13624)
* [oss-fuzz] UBSAN: shift exponent 35 is too large for 32-bit type
int in packet-netsync.c:467:25. ([41]Bug 13639)
* [oss-fuzz] UBSAN: shift exponent 32 is too large for 32-bit type
int in packet-sigcomp.c:3857:24. ([42]Bug 13641)
* [oss-fuzz] ASAN: stack-use-after-return
epan/dissectors/packet-ieee80211.c:14341:23 in add_tagged_field.
([43]Bug 13662)
* Welcome screen invalid capture filter wihtout WinPcap installed
causes runtime error. ([44]Bug 13672)
* SMB protocol parser does not parse SMB_COM_TRANSACTION2_SECONDARY
(0x33) command correctly. ([45]Bug 13690)
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
Bazaar, BT ATT, BT L2CAP, DHCP, DICOM, DNS, DWARF, IEEE 802.11, ISUP,
MSNIP, Netflow, Netsync, openSAFETY, OSITP, QUAKEWORLD, RGMP, RTCP,
SIGCOMP, SMB, SoulSeek, and XOT
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.
__________________________________________________________________
Getting Wireshark
Wireshark source code and installation packages are available from
[46]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 [47]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. ([48]Bug 1419)
The BER dissector might infinitely loop. ([49]Bug 1516)
Capture filters aren't applied when capturing from named pipes.
([50]Bug 1814)
Filtering tshark captures with read filters (-R) no longer works.
([51]Bug 2234)
Application crash when changing real-time option. ([52]Bug 4035)
Wireshark and TShark will display incorrect delta times in some cases.
([53]Bug 4985)
Wireshark should let you work with multiple capture files. ([54]Bug
10488)
Dell Backup and Recovery (DBAR) makes many Windows applications crash,
including Wireshark. ([55]Bug 12036)
__________________________________________________________________
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 2017-06-01 18:24:28 UTC
References
1. https://www.wireshark.org/security/wnpa-sec-2017-22.html
2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13599
3. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9352
4. https://www.wireshark.org/security/wnpa-sec-2017-24.html
5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13609
6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13628
7. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9351
8. https://www.wireshark.org/security/wnpa-sec-2017-25.html
9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13631
10. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9346
11. https://www.wireshark.org/security/wnpa-sec-2017-26.html
12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13633
13. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9345
14. https://www.wireshark.org/security/wnpa-sec-2017-27.html
15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13685
16. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9349
17. https://www.wireshark.org/security/wnpa-sec-2017-28.html
18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13649
19. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9350
20. https://www.wireshark.org/security/wnpa-sec-2017-29.html
21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13701
22. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9344
23. https://www.wireshark.org/security/wnpa-sec-2017-30.html
24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13725
25. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9343
26. https://www.wireshark.org/security/wnpa-sec-2017-32.html
27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13646
28. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9354
29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13164
30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13570
31. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13588
32. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13590
33. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13606
34. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13607
35. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13610
36. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13611
37. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13616
38. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13618
39. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13619
40. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13624
41. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13639
42. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13641
43. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13662
44. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13672
45. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13690
46. https://www.wireshark.org/download.html
47. https://www.wireshark.org/download.html#thirdparty
48. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
49. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
50. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
51. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
52. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
53. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
54. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
55. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12036
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.0.13.tar.bz2: 31268594 bytes
SHA256(wireshark-2.0.13.tar.bz2)=6bb8398edb7b59e7265b763aba54610c3f362af8a0ecfe6d4c9e51069687e243
RIPEMD160(wireshark-2.0.13.tar.bz2)=94de44a3cb997f421b31c2568bf291d5de44e155
SHA1(wireshark-2.0.13.tar.bz2)=ea0d3170570f1d4b2a70965e255b05675255be7a
MD5(wireshark-2.0.13.tar.bz2)=664328bf4f606a334168d1f3a9801b24
Wireshark-win32-2.0.13.exe: 44183496 bytes
SHA256(Wireshark-win32-2.0.13.exe)=64738da8fe5316ef2b90af7bb7821a2e05bc190baf99304c42f109b2e9405db8
RIPEMD160(Wireshark-win32-2.0.13.exe)=a056f7ae22768339d7a9d49f1c15bb5177bf3d15
SHA1(Wireshark-win32-2.0.13.exe)=5018bcba4a8442068468dbec354ecfb0e93e4246
MD5(Wireshark-win32-2.0.13.exe)=e9e6ba5d248d4521148504aba3ca3e42
Wireshark-win64-2.0.13.exe: 47804584 bytes
SHA256(Wireshark-win64-2.0.13.exe)=6968c556c2fc9c20bcec164407e85d84fe1804935bb3825bfcd1cfde93c4a010
RIPEMD160(Wireshark-win64-2.0.13.exe)=b0b756c854dc8e8f7a884afe0a22ad1315c887bc
SHA1(Wireshark-win64-2.0.13.exe)=973f46f5df7d87ee549b07f436f67be163ef324d
MD5(Wireshark-win64-2.0.13.exe)=a66dee5fdab4eb87bbded7c78589dde6
WiresharkPortable_2.0.13.paf.exe: 43864080 bytes
SHA256(WiresharkPortable_2.0.13.paf.exe)=6a3d42ee913ac1387f8e9266277d16899d238e0122deb1d4d78be6e19f6accea
RIPEMD160(WiresharkPortable_2.0.13.paf.exe)=41c286edd3a9f93f0fe46c50d8546c652926bb3e
SHA1(WiresharkPortable_2.0.13.paf.exe)=af613a62e5a6a1d3e02732df967f972013532794
MD5(WiresharkPortable_2.0.13.paf.exe)=32fd0935cd4a5deb4e59a58e2ab96694
Wireshark 2.0.13 Intel 64.dmg: 31777078 bytes
SHA256(Wireshark 2.0.13 Intel
64.dmg)=4e64c19dbeb6b649accc7e491574d441bd78be8e2e3c59bfb8dd75c1d26c94cf
RIPEMD160(Wireshark 2.0.13 Intel
64.dmg)=da9abed98e1af300500061e0ca854393262966e7
SHA1(Wireshark 2.0.13 Intel 64.dmg)=11867078cb5fe3eb65971fa3ca9ed7c53b36768c
MD5(Wireshark 2.0.13 Intel 64.dmg)=6c3ee6afa2b559af49148e370ea5df8f
Wireshark 2.0.13 Intel 32.dmg: 32527499 bytes
SHA256(Wireshark 2.0.13 Intel
32.dmg)=2f89e0903a50adba76f120629006df8db0cc5caac8a8f2f94cce0e957db1548d
RIPEMD160(Wireshark 2.0.13 Intel
32.dmg)=1d17d8e303a0a0704cedbdea5f0661a91aa9d14f
SHA1(Wireshark 2.0.13 Intel 32.dmg)=deeed00d9558d48922624210a6bb0e8675b499b7
MD5(Wireshark 2.0.13 Intel 32.dmg)=bc1dc1462e3825d7984ce10747f1e6ec
Attachment:
signature.asc
Description: OpenPGP digital signature
- Prev by Date: [Wireshark-users] Wireshark 2.2.7 is now available
- Next by Date: [Wireshark-users] Test message - ignore
- Previous by thread: [Wireshark-users] Wireshark 2.2.7 is now available
- Next by thread: [Wireshark-users] Test message - ignore
- Index(es):