Wireshark · Wireshark-announce: [Wireshark-announce] Wireshark 2.6.5 is now available

Wireshark-announce: [Wireshark-announce] Wireshark 2.6.5 is now available
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Wed, 28 Nov 2018 12:38:32 -0800
I'm proud to announce the release of Wireshark 2.6.5.


 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

    • The Windows installers now ship with Qt 5.9.7. Previously they
      shipped with Qt 5.9.5.

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2018-51[1] The Wireshark dissection engine could crash.
       Bug 14466[2]. CVE-2018-19625[3].

     • wnpa-sec-2018-52[4] The DCOM dissector could crash. Bug 15130[5].
       CVE-2018-19626[6].

     • wnpa-sec-2018-53[7] The LBMPDM dissector could crash. Bug
       15132[8]. CVE-2018-19623[9].

     • wnpa-sec-2018-54[10] The MMSE dissector could go into an infinite
       loop. Bug 15250[11]. CVE-2018-19622[12].

     • wnpa-sec-2018-55[13] The IxVeriWave file parser could crash. Bug
       15279[14]. CVE-2018-19627[15].

     • wnpa-sec-2018-56[16] The PVFS dissector could crash. Bug
       15280[17]. CVE-2018-19624[18].

     • wnpa-sec-2018-57[19] The ZigBee ZCL dissector could crash. Bug
       15281[20]. CVE-2018-19628[21].

   The following bugs have been fixed:

     • VoIP Calls dialog doesn’t include RTP stream when preparing a
       filter. Bug 13440[22].

     • Wireshark installs on macOS with permissions for
       /Library/Application Support/Wireshark that are too restrictive.
       Bug 14335[23].

     • Closing Enabled Protocols dialog crashes wireshark. Bug
       14349[24].

     • Unable to Export Objects → HTTP after sorting columns. Bug
       14545[25].

     • DNS Response to NS query shows as malformed packet. Bug
       14574[26].

     • Encrypted Alerts corresponds to a wrong selection in the packet
       bytes pane. Bug 14712[27].

     • Wireshark crashes/asserts with Qt 5.11.1 and assert/debugsymbols
       enabled. Bug 15014[28].

     • ESP will not decode since 2.6.2 - works fine in 2.4.6 or 2.4.8.
       Bug 15056[29].

     • text2pcap generates malformed packets when TCP, UDP or SCTP
       headers are added together with IPv6 header. Bug 15194[30].

     • Wireshark tries to decode EAP-SIM Pseudonym Identity. Bug
       15196[31].

     • Infinite read loop when extcap exits with error and error
       message. Bug 15205[32].

     • MATE unable to extract fields for PDU. Bug 15208[33].

     • Malformed Packet: SV. Bug 15224[34].

     • OPC UA Max nesting depth exceeded for valid packet. Bug
       15226[35].

     • TShark 2.6 does not print GeoIP information. Bug 15230[36].

     • ISUP (ANSI) packets malformed in WS versions later than 2.4.8.
       Bug 15236[37].

     • Handover candidate enquire message not decoded. Bug 15237[38].

     • TShark piping output in a cmd or PowerShell prompt stops working
       when GeoIP is enabled. Bug 15248[39].

     • ICMPv6 with routing header incorrectly placed. Bug 15270[40].

     • IEEE 802.11 Vendor Specific fixed fields display as malformed
       packets. Bug 15273[41].

     • text2pcap -4 and -6 option should require -i as well. Bug
       15275[42].

     • text2pcap direction sensitivity does not affect dummy ethernet
       addresses. Bug 15287[43].

     • MLE security suite display incorrect. Bug 15288[44].

     • Message for incorrect IPv4 option lengths is incorrect. Bug
       15290[45].

     • TACACS+ dissector does not properly reassemble large accounting
       messages. Bug 15293[46].

     • NLRI of S-PMSI A-D BGP route not being displayed. Bug 15307[47].

  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

   BGP, DCERPC, DCOM, DNS, EAP, ESP, GSM A BSSMAP, IEEE 802.11, IEEE
   802.11 Radiotap, IPv4, IPv6, ISUP, LBMPDM, LISP, MLE, MMSE, OpcUa,
   PVFS, SLL, SSL/TLS, SV, TACACS+, TCAP, Wi-SUN, XRA, and ZigBee ZCL

  New and Updated Capture File Support

   3GPP TS 32.423 Trace and IxVeriWave

  New and Updated Capture Interfaces support

   sshdump

 Getting Wireshark

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

  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[49] 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[50].

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

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

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

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

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

 Getting Help

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

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

 Frequently Asked Questions

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

  Last updated 2018-11-28 18:12:37 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2018-51
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14466
   3. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19625
   4. https://www.wireshark.org/security/wnpa-sec-2018-52
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15130
   6. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19626
   7. https://www.wireshark.org/security/wnpa-sec-2018-53
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15132
   9. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19623
  10. https://www.wireshark.org/security/wnpa-sec-2018-54
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15250
  12. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19622
  13. https://www.wireshark.org/security/wnpa-sec-2018-55
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15279
  15. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19627
  16. https://www.wireshark.org/security/wnpa-sec-2018-56
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15280
  18. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19624
  19. https://www.wireshark.org/security/wnpa-sec-2018-57
  20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15281
  21. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19628
  22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13440
  23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14335
  24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14349
  25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14545
  26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14574
  27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14712
  28. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15014
  29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15056
  30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15194
  31. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15196
  32. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15205
  33. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15208
  34. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15224
  35. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15226
  36. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15230
  37. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15236
  38. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15237
  39. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15248
  40. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15270
  41. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15273
  42. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15275
  43. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15287
  44. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15288
  45. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15290
  46. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15293
  47. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15307
  48. https://www.wireshark.org/download.html
  49. https://www.wireshark.org/download.html#thirdparty
  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.6.5.tar.xz: 28390292 bytes
SHA256(wireshark-2.6.5.tar.xz)=93155b798544b2f07693920f4ac1b531c952965ee4eb1d98419961240177438a
RIPEMD160(wireshark-2.6.5.tar.xz)=0f840f0ef8747ba808ac17660bb54f3ff9dfdc4b
SHA1(wireshark-2.6.5.tar.xz)=556a8e084230e6359c86daf578d25c6f443458bb

Wireshark-win32-2.6.5.exe: 53798712 bytes
SHA256(Wireshark-win32-2.6.5.exe)=9c9a459cec8866b82f68e35d6376d6d121123f3551bd83a17b36193e32828d2f
RIPEMD160(Wireshark-win32-2.6.5.exe)=7e7a667c9169075f23bf28b4b39604396a89b529
SHA1(Wireshark-win32-2.6.5.exe)=333556211a0e48eff4778404b809d3fb49414b8b

Wireshark-win64-2.6.5.exe: 59537312 bytes
SHA256(Wireshark-win64-2.6.5.exe)=1ee5afdc18efda2781a88da6a360a28ae88feaaecdc7c3246fb98767abcc7654
RIPEMD160(Wireshark-win64-2.6.5.exe)=65e9962f4c52af124a657e157fb91ee303affa2e
SHA1(Wireshark-win64-2.6.5.exe)=126b32d7e11bfb42b86c87920ea231e213defc5c

Wireshark-win32-2.6.5.msi: 43286528 bytes
SHA256(Wireshark-win32-2.6.5.msi)=a63cbb2da79ef80ae8855ef4cfbd92285de9655833e2dd1897d84cdb83246141
RIPEMD160(Wireshark-win32-2.6.5.msi)=8ebabf8958167bd68a69a754cc36a0f008a1b354
SHA1(Wireshark-win32-2.6.5.msi)=1b74d74a9c9d54d7507be198c891ab00905931f6

Wireshark-win64-2.6.5.msi: 48926720 bytes
SHA256(Wireshark-win64-2.6.5.msi)=3882cabc355ee298e4a8e6940cc67c286c349b85e76dfc63fe532f0555cba004
RIPEMD160(Wireshark-win64-2.6.5.msi)=d49c115e92373529049e7689ba693e8101dad9de
SHA1(Wireshark-win64-2.6.5.msi)=0433bbf10eef0b0d8949a6145c4ebcfdfbf49e6a

WiresharkPortable_2.6.5.paf.exe: 37034016 bytes
SHA256(WiresharkPortable_2.6.5.paf.exe)=2c6e3831da69c840f7904deb05542984c03f0de9d3979487ef7a557308c3b1a6
RIPEMD160(WiresharkPortable_2.6.5.paf.exe)=214876b0f4b7a8f7fac79591b777fad243c6e5c6
SHA1(WiresharkPortable_2.6.5.paf.exe)=f52d430442028a2d1da33c0fad98e353128f8f10

Wireshark 2.6.5 Intel 64.dmg: 168574656 bytes
SHA256(Wireshark 2.6.5 Intel
64.dmg)=b4e2cb6c9ddb0f700ef8eaba9f19248f92069a27622620646f46640e294c678f
RIPEMD160(Wireshark 2.6.5 Intel
64.dmg)=93e33202129eb42165324451e6065b62560c76ab
SHA1(Wireshark 2.6.5 Intel 64.dmg)=0b0cef24d1b1d5aaf13f6b918c24e187aac6a8b9

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
Next by Date: [Wireshark-announce] Wireshark 2.4.11 is now available
Next by thread: [Wireshark-announce] Wireshark 2.4.11 is now available
Index(es):
- Date
- Thread