Wireshark-users: [Wireshark-users] Wireshark 2.6.2 is now available

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 18 Jul 2018 14:38:23 -0700
I'm proud to announce the release of Wireshark 2.6.2.


 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:

     • wnpa-sec-2018-34[1]

     • BGP dissector large loop. Bug 13741[2]. CVE-2018-14342[3].

     • wnpa-sec-2018-35[4]

     • ISMP dissector crash. Bug 14672[5]. CVE-2018-14344[6].

     • wnpa-sec-2018-36[7]

     • Multiple dissectors could crash. Bug 14675[8]. CVE-2018-14340[9].

     • wnpa-sec-2018-37[10]

     • ASN.1 BER dissector crash. Bug 14682[11]. CVE-2018-14343[12].

     • wnpa-sec-2018-38[13]

     • MMSE dissector infinite loop. Bug 14738[14]. CVE-2018-14339[15].

     • wnpa-sec-2018-39[16]

     • DICOM dissector crash. Bug 14742[17]. CVE-2018-14341[18].

     • wnpa-sec-2018-40[19]

     • Bazaar dissector infinite loop. Bug 14841[20].
       CVE-2018-14368[21].

     • wnpa-sec-2018-41[22]

     • HTTP2 dissector crash. Bug 14869[23]. CVE-2018-14369[24].

     • wnpa-sec-2018-42[25]

     • CoAP dissector crash. Bug 14966[26]. CVE-2018-14367[27].

   The following bugs have been fixed:

     • ISMP.EDP "Tuples" dissected incorrectly. Bug 4943[28].

     • Wireshark - Race issue when switching between files using
       Wireshark’s "Files in Set" dialog. Bug 10870[29].

     • Sorting on "Source port" or "Destination port" column sorts
       alphabetically, not numerically. Bug 11460[30].

     • Wireshark crashes when changing profiles. Bug 11648[31].

     • Crash when starting capture while saving capture file or
       rescanning file after display filter change. Bug 13594[32].

     • Crash when switching to TRANSUM enabled profile. Bug 13697[33].

     • TCP retransmission with additional payload leads to incorrect
       bytes and length in stream. Bug 13700[34].

     • Wireshark crashes with single quote string display filter. Bug
       14084[35].

     • randpkt can write packets that libwiretap can’t read. Bug
       14107[36].

     • Wireshark crashes when loading new file before previous load has
       finished. Bug 14351[37].

     • Valid packet produces Malformed Packet: OpcUa. Bug 14465[38].

     • Error received from dissect_wccp2_hash_assignment_info(). Bug
       14573[39].

     • CRC checker wrong for FPP. Bug 14610[40].

     • Cross-build broken due to make-dissectors and make-taps. Bug
       14622[41].

     • Extraction of SMB file results in wrong size. Bug 14662[42].

     • 6LoWPAN dissector merges fragments from different sources. Bug
       14700[43].

     • IP address to name resolution doesn’t work in TShark. Bug
       14711[44].

     • "Decode as" Modbus RTU over USB doesn’t work with 2.6.0 but with
       2.4.6. Bug 14717[45].

     • proto_tree_add_protocol_format might leak memory. Bug 14719[46].

     • tostring for NSTime objects in lua gives wrong results. Bug
       14720[47].

     • Media type "application/octet-stream" registered for both Thread
       and UASIP. Bug 14729[48].

     • Crash related to SCTP tap. Bug 14733[49].

     • Formatting of OSI area addresses/address prefixes goes past the
       end of the area address/address prefix. Bug 14744[50].

     • ICMPv6 Router Renumbering - Packet Dissector - malformed. Bug
       14755[51].

     • WiMAX HARQ MAP decoder segfaults when length is too short. Bug
       14780[52].

     • HTTP PUT request following a HEAD request is not correctly
       decoded. Bug 14793[53].

     • SYNC PDU type 3 miss the last PDU length. Bug 14823[54].

     • Reversed 128 bits service UUIDs when Bluetooth Low Energy
       advertisement data are dissected. Bug 14843[55].

     • Issues with Wireshark when the user doesn’t have permission to
       capture. Bug 14847[56].

     • Wrong description when LE Bluetooth Device Address type is
       dissected. Bug 14866[57].

     • LE Role advertisement type (0x1c) is not dissected properly
       according to the Bluetooth specification. Bug 14868[58].

     • Regression: Wireshark 2.6.0 and 2.6.1 are unable to read NetMon
       files which were readable by previous versions. Bug 14876[59].

     • Wireshark doesn’t properly display (deliberately) invalid 220
       responses from Postfix. Bug 14878[60].

     • Follow TCP Stream and click reassembled content moves you to
       incorrect current packet. Bug 14898[61].

     • Crash when changing profiles while loading a capture file. Bug
       14918[62].

     • Duplicate PDU during C Arrays Output Export. Bug 14933[63].

     • DCE/RPC not dissected when "reserved for use by implementations"
       flag bits set. Bug 14942[64].

     • Follow TCP Stream truncates output on missing (but ACKed)
       segments. Bug 14944[65].

     • There’s no option to include column headings when printing
       packets or exporting packet dissections with Qt Wireshark. Bug
       14945[66].

     • Qt: SCTP Graph Dialog: Abort when doing analysis. Bug 14971[67].

     • CMake is unable to find LUA libraries. Bug 14983[68].

  New and Updated Features

   There are no new features in this release.

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   6LoWPAN, ASN.1 BER, Bazaar, BGP, Bluetooth, Bluetooth HCI_CMD, CIGI,
   Cisco ttag, CoAP, Data, DCERPC, Diameter 3GPP, DICOM, DOCSIS, FPP,
   GSM A GM, GTPv2, HTTP, HTTP2, IAX2, ICMPv6, IEEE 1722, IEEE 802.11,
   IPv4, ISMP, LISP, MMSE, MTP3, MySQL, NFS, OpcUa, PPI GPS, Q.931,
   RNSAP, RPCoRDMA, S1AP, SCTP, SMB, SMTP, STUN, SYNC, T.30, TCP,
   TRANSUM, WAP, WCCP, Wi-SUN, WiMax HARQ Map Message, and WSP

  New and Updated Capture File Support

   Alcatel-Lucent Ascend and Microsoft Network Monitor

  New and Updated Capture Interfaces support

   There is no new or updated capture file support in this release.

 Getting Wireshark

  Wireshark source code and installation packages are available from
  https://www.wireshark.org/download.html[69].

  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 download page[70] 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

  The BER dissector might infinitely loop. Bug 1516[71].

  Capture filters aren’t applied when capturing from named pipes. Bug
  1814[72].

  Filtering tshark captures with read filters (-R) no longer works. Bug
  2234[73].

  Application crash when changing real-time option. Bug 4035[74].

  Wireshark and TShark will display incorrect delta times in some cases.
  Bug 4985[75].

  Wireshark should let you work with multiple capture files. Bug
  10488[76].

 Getting Help

  Community support is available on Wireshark’s Q&A site[77] 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[78].

  Official Wireshark training and certification are available from
  Wireshark University[79].

 Frequently Asked Questions

  A complete FAQ is available on the Wireshark web site[80].

  Last updated 2018-07-18 20:55:10 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2018-34
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13741
   3. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14342
   4. https://www.wireshark.org/security/wnpa-sec-2018-35
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14672
   6. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14344
   7. https://www.wireshark.org/security/wnpa-sec-2018-36
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14675
   9. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14340
  10. https://www.wireshark.org/security/wnpa-sec-2018-37
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14682
  12. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14343
  13. https://www.wireshark.org/security/wnpa-sec-2018-38
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14738
  15. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14339
  16. https://www.wireshark.org/security/wnpa-sec-2018-39
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14742
  18. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14341
  19. https://www.wireshark.org/security/wnpa-sec-2018-40
  20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14841
  21. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14368
  22. https://www.wireshark.org/security/wnpa-sec-2018-41
  23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14869
  24. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14369
  25. https://www.wireshark.org/security/wnpa-sec-2018-42
  26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14966
  27. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14367
  28. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4943
  29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10870
  30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11460
  31. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11648
  32. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13594
  33. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13697
  34. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13700
  35. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14084
  36. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14107
  37. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14351
  38. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14465
  39. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14573
  40. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14610
  41. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14622
  42. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14662
  43. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14700
  44. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14711
  45. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14717
  46. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14719
  47. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14720
  48. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14729
  49. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14733
  50. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14744
  51. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14755
  52. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14780
  53. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14793
  54. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14823
  55. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14843
  56. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14847
  57. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14866
  58. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14868
  59. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14876
  60. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14878
  61. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14898
  62. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14918
  63. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14933
  64. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14942
  65. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14944
  66. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14945
  67. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14971
  68. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14983
  69. https://www.wireshark.org/download.html
  70. https://www.wireshark.org/download.html#thirdparty
  71. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
  72. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
  73. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  74. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  75. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  76. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  77. https://ask.wireshark.org/
  78. https://www.wireshark.org/lists/
  79. http://www.wiresharktraining.com/
  80. https://www.wireshark.org/faq.html


Digests

wireshark-2.6.2.tar.xz: 28392140 bytes
SHA256(wireshark-2.6.2.tar.xz)=49b2895ee3ba17ef9ef0aebfdc4d32a778e0f36ccadde184516557d5f3357094
RIPEMD160(wireshark-2.6.2.tar.xz)=e9b782d49d9a063ba556320e9f2c08dea079967d
SHA1(wireshark-2.6.2.tar.xz)=52517c30926211b0b718815b51a3f06a18d8f5da

Wireshark-win64-2.6.2.exe: 59963968 bytes
SHA256(Wireshark-win64-2.6.2.exe)=88aa2ca018090fc73ffb273aa1ba9f690ec06deb77d1ec7ff9b39fe646ca2877
RIPEMD160(Wireshark-win64-2.6.2.exe)=3b947ada3e64bfb1c1b16a470926d94ed9db391b
SHA1(Wireshark-win64-2.6.2.exe)=90217eb0ed020a53a9ae80682c0881d347d11b4a

Wireshark-win32-2.6.2.exe: 54249888 bytes
SHA256(Wireshark-win32-2.6.2.exe)=3d886e435570b7326f53d00996040ef65b9e2a5bffe48645ce29ea5a23930801
RIPEMD160(Wireshark-win32-2.6.2.exe)=c2c5afa101559976439f36401ea1cc4564fa624e
SHA1(Wireshark-win32-2.6.2.exe)=eb7c50e80d6e7ec834599c1facfd6a3fd66aebf8

Wireshark-win32-2.6.2.msi: 43728896 bytes
SHA256(Wireshark-win32-2.6.2.msi)=99d5d94345a20e177736533840ff59859a76e864247a8146a73fca227f004043
RIPEMD160(Wireshark-win32-2.6.2.msi)=7f21412e4d335f6e797356b968fbef14afb03b8c
SHA1(Wireshark-win32-2.6.2.msi)=05f1f9c4b9bed8c4447e5e31f907c578f52cf067

Wireshark-win64-2.6.2.msi: 49364992 bytes
SHA256(Wireshark-win64-2.6.2.msi)=381076d09c757038072f761f7eee9d5aa45fa8423b771ba34ddbd8b56f2c429c
RIPEMD160(Wireshark-win64-2.6.2.msi)=a080eec0f8bd089f493d0c76837d7fe03c1fa0dd
SHA1(Wireshark-win64-2.6.2.msi)=2c6b5bf555729d1e5ee3a1dda8d2b14d3bb01759

WiresharkPortable_2.6.2.paf.exe: 37482552 bytes
SHA256(WiresharkPortable_2.6.2.paf.exe)=d36727bdb8cc3a72bfb80084d3c634c3bfa4661f4de68d644b43ef5d41c52b69
RIPEMD160(WiresharkPortable_2.6.2.paf.exe)=a98756bf5a67e47e1ca9ecd8836f2e6913a56f27
SHA1(WiresharkPortable_2.6.2.paf.exe)=dd11e62f34212be77abee9d2227a2fd3b613b0a5

Wireshark 2.6.2 Intel 64.dmg: 169012317 bytes
SHA256(Wireshark 2.6.2 Intel
64.dmg)=ef54b04a73df4069e29e77bc1940f3b767ee498c4e28f739eabda78ef71ab4a9
RIPEMD160(Wireshark 2.6.2 Intel
64.dmg)=f93d2cc4057337ca76d1aa435b0039a60927bebb
SHA1(Wireshark 2.6.2 Intel 64.dmg)=3a46de720848b286e7c115c75c7b00bcd08155aa

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