[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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


 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 might 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-22[3] iSCSI dissector crash. Issue 19164[4].
       CVE-2023-3649[5].

     • wnpa-sec-2023-24[6] BT SDP dissector infinite loop. Issue
       19258[7].

     • wnpa-sec-2023-25[8] BT SDP dissector memory leak. Issue 19259[9].

     • wnpa-sec-2023-26[10] CP2179 dissector crash. Issue 19229[11].

   The following bugs have been fixed:

     • Wireshark wrongly blames group membership when pcap capabilities
       are removed. Issue 18279[12].

     • Packet bytes window broken layout. Issue 18326[13].

     • Valid Ethernet CFM DMM packets are shown as malformed. Issue
       19198[14].

     • The QUIC dissector is reporting the quic_transport_parameters
       max_ack_delay with the title "GREASE". Issue 19209[15].

     • Preferences: Folder name editing behaves weirdly, cursor jumps.
       Issue 19213[16].

     • DHCPFO: Expert info list does not show all expert infos. Issue
       19216[17].

     • Applying color filtering fails when selecting the same field to
       color (i.e., changing frames without focusing in packet details).
       Issue 19249[18].

     • NAS 5GS Malformed Packet Decoding SOR transparent container PLMN
       ID and access technology list. Issue 19273[19].

  New and Updated Features

   There are no new or updated features in this release.

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   BT SDP, CP2179, CQL, DHCPFO, F1AP, GSM DTAP, IEEE 802.11, NAS-5GS,
   PFCP, and TFTP

  New and Updated Capture File Support

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

  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[20] 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[21] 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[22].

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

 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[24].

 Frequently Asked Questions

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

 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-22
   4. https://gitlab.com/wireshark/wireshark/-/issues/19164
   5. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3649
   6. https://www.wireshark.org/security/wnpa-sec-2023-24
   7. https://gitlab.com/wireshark/wireshark/-/issues/19258
   8. https://www.wireshark.org/security/wnpa-sec-2023-25
   9. https://gitlab.com/wireshark/wireshark/-/issues/19259
  10. https://www.wireshark.org/security/wnpa-sec-2023-26
  11. https://gitlab.com/wireshark/wireshark/-/issues/19229
  12. https://gitlab.com/wireshark/wireshark/-/issues/18279
  13. https://gitlab.com/wireshark/wireshark/-/issues/18326
  14. https://gitlab.com/wireshark/wireshark/-/issues/19198
  15. https://gitlab.com/wireshark/wireshark/-/issues/19209
  16. https://gitlab.com/wireshark/wireshark/-/issues/19213
  17. https://gitlab.com/wireshark/wireshark/-/issues/19216
  18. https://gitlab.com/wireshark/wireshark/-/issues/19249
  19. https://gitlab.com/wireshark/wireshark/-/issues/19273
  20. https://www.wireshark.org/download.html
  21. https://ask.wireshark.org/
  22. https://www.wireshark.org/lists/
  23. https://gitlab.com/wireshark/wireshark/-/issues
  24. https://wiresharkfoundation.org
  25. https://www.wireshark.org/faq.html


Digests

wireshark-3.6.16.tar.xz: 40239364 bytes
SHA256(wireshark-3.6.16.tar.xz)=72d29297b23468434b6dd7c29114e5c2bc9ca84c04249fb5e433a0229fbe1033
SHA1(wireshark-3.6.16.tar.xz)=71a780167376e20d09b945256fa9f394493f5e8e

Wireshark-win32-3.6.16.exe: 61338256 bytes
SHA256(Wireshark-win32-3.6.16.exe)=4f30d190d0193b21a31f697d407e6e9e7d1e601ef78db68132d0a9e5fbebf5a6
SHA1(Wireshark-win32-3.6.16.exe)=8d34da62c1470869a1e3ae552b8a30290e7fe4d9

Wireshark-win64-3.6.16.exe: 77570216 bytes
SHA256(Wireshark-win64-3.6.16.exe)=a4477860d973e50e9b11f0bb753691862e2a8843f82c32144657bb27aa99819c
SHA1(Wireshark-win64-3.6.16.exe)=a94894d4c56a4aa7575d2cb25428d130e428e4bc

Wireshark-win64-3.6.16.msi: 51851264 bytes
SHA256(Wireshark-win64-3.6.16.msi)=2a07a6a753a5a81fff95aa5d3a43f547282e95b67ff7b05da54e8d9a83c7e17c
SHA1(Wireshark-win64-3.6.16.msi)=3f861079a87fe7c0393637f3db0df8be1973e7c8

Wireshark-win32-3.6.16.msi: 45834240 bytes
SHA256(Wireshark-win32-3.6.16.msi)=6f544a81eae308aa05cc186df80366b3c38bad0e0e831988063c4c792d401f4b
SHA1(Wireshark-win32-3.6.16.msi)=62f8ab4ba55c75e35bbf3b4239e0dd9ce7c747b3

WiresharkPortable32_3.6.16.paf.exe: 39836168 bytes
SHA256(WiresharkPortable32_3.6.16.paf.exe)=4a31d5c24f0e99e12f8d674b29483643fab5f8e2d9cbd06945457bc058574a97
SHA1(WiresharkPortable32_3.6.16.paf.exe)=5cd35977cccef4e6bb16f26035346fd44d537a57

WiresharkPortable64_3.6.16.paf.exe: 44587632 bytes
SHA256(WiresharkPortable64_3.6.16.paf.exe)=1183d1424566fa810cd4d7cb70a44871b5df05f5b4998f64175287cf31039a24
SHA1(WiresharkPortable64_3.6.16.paf.exe)=463b6647192ecbabc6174394fc995840fd9a84ec

Wireshark 3.6.16 Arm 64.dmg: 141932132 bytes
SHA256(Wireshark 3.6.16 Arm 64.dmg)=701fdb64d2bd3951f96389f2f1d173df99f97cac7505d30a35777965115bb5b1
SHA1(Wireshark 3.6.16 Arm 64.dmg)=536f90d6a2e72870b94f03da8371e1a16b796250

Wireshark 3.6.16 Intel 64.dmg: 142177261 bytes
SHA256(Wireshark 3.6.16 Intel 64.dmg)=3d09b2fd7b146edb4b365ec939f7d143ee001043bd5a28c0c88d6857b675ed31
SHA1(Wireshark 3.6.16 Intel 64.dmg)=7ecce5ef23467c7da5bc7d9e617c83645b7ea07b

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

Attachment: OpenPGP_signature
Description: OpenPGP digital signature