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

[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

I'm proud to announce the release of Wireshark 3.6.14.


 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

  This is the last release branch with support for 32-bit Windows.
  Updates will no longer be available after May 22, 2024 for that
  platform. Issue 17779[1]

  If you’re running Wireshark on macOS and upgraded to macOS 13 from an
  earlier version, you will likely have to open and run the “Uninstall
  ChmodBPF” package, then open and run “Install ChmodBPF” in order to
  reset the ChmodBPF Launch Daemon. Issue 18734[2].

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2023-12[3] Candump log file parser crash. Issue
       19062[4].

     • wnpa-sec-2023-13[5] BLF file parser crash. Issue 19063[6].

     • wnpa-sec-2023-14[7] GDSDB dissector infinite loop. Issue
       19068[8].

     • wnpa-sec-2023-15[9] NetScaler file parser crash. Issue 19081[10].

     • wnpa-sec-2023-16[11] VMS TCPIPtrace file parser crash. Issue
       19083[12].

     • wnpa-sec-2023-19[13] IEEE C37.118 Synchrophasor dissector crash.
       Issue 19087[14]. CVE-2023-0668[15].

     • IEEE-C37.118 parsing buffer overflow. Issue 19087[16].

   The following bugs have been fixed:

     • Incorrect padding in BFCP decoder Issue 18890[17].

     • SPNEGO dissector bug Issue 18991[18].

     • SRT values are incorrect when applying a time shift. Issue
       18999[19].

     • batadv dissector bug Issue 19047[20].

     • [UDS] When filtering the uds.wdbi.data_identifier or
       uds.iocbi.data_identifier field is interpreted as 1 byte whereas
       it consists of 2 bytes Issue 19078[21].

     • Wireshark can’t save this capture in that format Issue 19080[22].

     • MSMMS parsing buffer overflow Issue 19086[23].

     • USB HID parser shows wrong label for usages Rx/Vx/Vbrx of usage
       page Generic Desktop Control Issue 19095[24].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   batadv, BFCP, CommunityID, COSE, GDSDB, ILP, ISAKMP, MSMMS, NTLMSSP,
   SPNEGO, Synphasor, TCP, UDS, ULP, and USB HID

  New and Updated Capture File Support

   BLF, Candump, NetScaler, and VMS TCPIPtrace

  New File Format Decoding Support

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

 Getting Wireshark

  Wireshark source code and installation packages are available from
  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 download page[25] 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 "Help › About
  Wireshark › Folders" or `tshark -G folders` to find the default
  locations on your system.

 Getting Help

  The User’s Guide, manual pages and various other documentation can be
  found at https://www.wireshark.org/docs/

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

  Bugs and feature requests can be reported on the issue tracker[28].

 How You Can Help

  The Wireshark Foundation helps as many people as possible understand
  their networks as much as possible. You can find out more and donate
  at wiresharkfoundation.org[29].

 Frequently Asked Questions

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

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17779
   2. https://gitlab.com/wireshark/wireshark/-/issues/18734
   3. https://www.wireshark.org/security/wnpa-sec-2023-12
   4. https://gitlab.com/wireshark/wireshark/-/issues/19062
   5. https://www.wireshark.org/security/wnpa-sec-2023-13
   6. https://gitlab.com/wireshark/wireshark/-/issues/19063
   7. https://www.wireshark.org/security/wnpa-sec-2023-14
   8. https://gitlab.com/wireshark/wireshark/-/issues/19068
   9. https://www.wireshark.org/security/wnpa-sec-2023-15
  10. https://gitlab.com/wireshark/wireshark/-/issues/19081
  11. https://www.wireshark.org/security/wnpa-sec-2023-16
  12. https://gitlab.com/wireshark/wireshark/-/issues/19083
  13. https://www.wireshark.org/security/wnpa-sec-2023-19
  14. https://gitlab.com/wireshark/wireshark/-/issues/19087
  15. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0668
  16. https://gitlab.com/wireshark/wireshark/-/issues/19087
  17. https://gitlab.com/wireshark/wireshark/-/issues/18890
  18. https://gitlab.com/wireshark/wireshark/-/issues/18991
  19. https://gitlab.com/wireshark/wireshark/-/issues/18999
  20. https://gitlab.com/wireshark/wireshark/-/issues/19047
  21. https://gitlab.com/wireshark/wireshark/-/issues/19078
  22. https://gitlab.com/wireshark/wireshark/-/issues/19080
  23. https://gitlab.com/wireshark/wireshark/-/issues/19086
  24. https://gitlab.com/wireshark/wireshark/-/issues/19095
  25. https://www.wireshark.org/download.html
  26. https://ask.wireshark.org/
  27. https://www.wireshark.org/lists/
  28. https://gitlab.com/wireshark/wireshark/-/issues
  29. https://wiresharkfoundation.org
  30. https://www.wireshark.org/faq.html


Digests

wireshark-3.6.14.tar.xz: 40211952 bytes
SHA256(wireshark-3.6.14.tar.xz)=0a8f7bc23056b3e93dc33b9f12241fc487f73259e7299bd20109e84c4bdfc687
SHA1(wireshark-3.6.14.tar.xz)=9b45beb82cbf4cb4470597e286daa1b0add443b6

Wireshark-win32-3.6.14.exe: 61179392 bytes
SHA256(Wireshark-win32-3.6.14.exe)=6335c33e96fba07bbfc6c4b17fdce5c0c47e49094385b21a0de54eb6c6953dfa
SHA1(Wireshark-win32-3.6.14.exe)=9512f774a25fbf98548db628cb35f5634a02cc65

Wireshark-win64-3.6.14.exe: 77377504 bytes
SHA256(Wireshark-win64-3.6.14.exe)=9672b1fab6bd3c372171dd7b5c70f17cb6269d861ef6b3c68b68d81133ddd611
SHA1(Wireshark-win64-3.6.14.exe)=dd02a2f7bb238d524f06b6416411fcd866f50f51

Wireshark-win64-3.6.14.msi: 51122176 bytes
SHA256(Wireshark-win64-3.6.14.msi)=9ab0edda0b27cce2db99847a233c606629e1050d7f92b253b4e18a8080b30507
SHA1(Wireshark-win64-3.6.14.msi)=a73b2b1fe98930ae664463111668c0f416d60fd2

Wireshark-win32-3.6.14.msi: 45748224 bytes
SHA256(Wireshark-win32-3.6.14.msi)=cb10d50dce06c2316a2399424ddc53b1bf12d1f5718b3702f07c6cb46fc3c8d2
SHA1(Wireshark-win32-3.6.14.msi)=922acce77b3d7933cf5f520a33b45d197c859402

WiresharkPortable32_3.6.14.paf.exe: 39768648 bytes
SHA256(WiresharkPortable32_3.6.14.paf.exe)=11e160fbd5401ddaf0c0720a72e0cc5b5602b225a792ca26c22e4c4ee9817f9d
SHA1(WiresharkPortable32_3.6.14.paf.exe)=18162a68c4cd781bc51c2570c62747b0136fa3ea

WiresharkPortable64_3.6.14.paf.exe: 44509512 bytes
SHA256(WiresharkPortable64_3.6.14.paf.exe)=df0b8d85828cc7ceb9f0da9aa586b366db1590a8b336bea88da5318f0e1dacdd
SHA1(WiresharkPortable64_3.6.14.paf.exe)=b2e81b70c2d782725df493f28e6d35d690ce7d02

Wireshark 3.6.14 Arm 64.dmg: 141859761 bytes
SHA256(Wireshark 3.6.14 Arm 64.dmg)=6737778ba625b2583277d5e99585ea31f5af71f8a372bedbf0534c2407c504ac
SHA1(Wireshark 3.6.14 Arm 64.dmg)=cc99e75382fc3b2016fabb8f1f3806a2f22b3f83

Wireshark 3.6.14 Intel 64.dmg: 142104941 bytes
SHA256(Wireshark 3.6.14 Intel 64.dmg)=b45b2cdf41bd9c6f0214587d0420ee6f21fa548ffc30b8b9acd8229b50825eea
SHA1(Wireshark 3.6.14 Intel 64.dmg)=8ceeab9a5bd5a38c1bb51700c4f6491a4e166782

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 Arm 64.dmg"
    Other: openssl sha256 wireshark-x.y.z.tar.xz