[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

I'm proud to announce the release of Wireshark 3.6.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

  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-09[3] RPCoRDMA dissector crash. Issue 18852[4].
       CVE-2023-1992[5].

     • wnpa-sec-2023-10[6] LISP dissector large loop. Issue 18900[7].
       CVE-2023-1993[8].

     • wnpa-sec-2023-11[9] GQUIC dissector crash Issue 18947[10].
       CVE-2023-1994[11].

   The following bugs have been fixed:

     • Wireshark ITS Dissector RTCMEM wrong protocol version selector 2
       - should use 1 Issue 18862[12].

     • Wireshark treats the letter E in SSRC as an exponential
       representation of a number Issue 18879[13].

     • VNC RRE Parser skips over data Issue 18883[14].

     • Fuzz job crash output: fuzz-2023-03-27-7564.pcap Issue 18934[15].

     • Fuzz job crash output: fuzz-2023-03-31-6903.pcap Issue 18947[16].

     • RTP analysis shows incorrect timestamp error when timestamp is
       rolled over Issue 18973[17].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   DNS, ERF, FF, genl, GQUIC, GSM A-bis OML, HL7, IEEE 802.11, ITS, ITS,
   LISP, netlink, netlink-netfilter, netlink-sock_diag, nl80211, RLC,
   RPCoRDMA, RTPS, SCTP, SMB, VNC, and WCP

  New and Updated Capture File Support

   Netmon and NetScaler

  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[18] 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[19] 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[20].

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

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

 Frequently Asked Questions

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

 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-09
   4. https://gitlab.com/wireshark/wireshark/-/issues/18852
   5. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1992
   6. https://www.wireshark.org/security/wnpa-sec-2023-10
   7. https://gitlab.com/wireshark/wireshark/-/issues/18900
   8. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1993
   9. https://www.wireshark.org/security/wnpa-sec-2023-11
  10. https://gitlab.com/wireshark/wireshark/-/issues/18947
  11. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1994
  12. https://gitlab.com/wireshark/wireshark/-/issues/18862
  13. https://gitlab.com/wireshark/wireshark/-/issues/18879
  14. https://gitlab.com/wireshark/wireshark/-/issues/18883
  15. https://gitlab.com/wireshark/wireshark/-/issues/18934
  16. https://gitlab.com/wireshark/wireshark/-/issues/18947
  17. https://gitlab.com/wireshark/wireshark/-/issues/18973
  18. https://www.wireshark.org/download.html
  19. https://ask.wireshark.org/
  20. https://www.wireshark.org/lists/
  21. https://gitlab.com/wireshark/wireshark/-/issues
  22. https://wiresharkfoundation.org
  23. https://www.wireshark.org/faq.html


Digests

wireshark-3.6.13.tar.xz: 39982176 bytes
SHA256(wireshark-3.6.13.tar.xz)=4e251b0b9a23554745c93d68d3073b92e880f1918ee482208c620335c1bd6004
SHA1(wireshark-3.6.13.tar.xz)=972fcdaf1057227ec3d292454e5de73e70f62fa0

Wireshark-win64-3.6.13.exe: 77376592 bytes
SHA256(Wireshark-win64-3.6.13.exe)=f5de08a7cca07cba8e9cb1c586a93f2894b0f538755c5db7b89a3566b1d3b110
SHA1(Wireshark-win64-3.6.13.exe)=ce2cca3360294bf077170998d32f9c8a7408a5b4

Wireshark-win32-3.6.13.exe: 61178368 bytes
SHA256(Wireshark-win32-3.6.13.exe)=3fea0f2e6dd037a1a06b5e9e70fee317536d84fc07e01817a08299eb2dfef6f5
SHA1(Wireshark-win32-3.6.13.exe)=156c3eb5fcac39b95e9475a507d620c92bc5480a

Wireshark-win32-3.6.13.msi: 45735936 bytes
SHA256(Wireshark-win32-3.6.13.msi)=fb6edb1236c2323924891c1680e8ef3fe86b39c62f698c0278ba99630cb39cb3
SHA1(Wireshark-win32-3.6.13.msi)=0631ccb3b53e586dccccdbf8ddbc50ef06212b04

Wireshark-win64-3.6.13.msi: 51134464 bytes
SHA256(Wireshark-win64-3.6.13.msi)=04f4c653bef0fd670254a6c7096df625cd2b1fbc0106b0ca3be228d72bff18c8
SHA1(Wireshark-win64-3.6.13.msi)=d91c28f95d08c401636a39e4945a306e7732aaf3

WiresharkPortable32_3.6.13.paf.exe: 39758048 bytes
SHA256(WiresharkPortable32_3.6.13.paf.exe)=abbd0150cd74eb82a0924e164bde1f130d1d8aff38f83378dda3241baf9f36c5
SHA1(WiresharkPortable32_3.6.13.paf.exe)=0b7189730bbcb3d1115048ae3edb826245a141a1

WiresharkPortable64_3.6.13.paf.exe: 44503616 bytes
SHA256(WiresharkPortable64_3.6.13.paf.exe)=d292c9e7c6d524e570daa61f41bc1d957d6796181baf3ece9261187ae9c6acb9
SHA1(WiresharkPortable64_3.6.13.paf.exe)=dbdc62941f3a5d0c5b96345d0c2f7bde3605528f

Wireshark 3.6.13 Arm 64.dmg: 141855513 bytes
SHA256(Wireshark 3.6.13 Arm 64.dmg)=7b1bb9fc1d22a56df4ae51ac27a0847dc1ab56de35ac156540d0a87a586f5225
SHA1(Wireshark 3.6.13 Arm 64.dmg)=7c62bf381a109a0fa798da3fc6853a00548025d7

Wireshark 3.6.13 Intel 64.dmg: 142103965 bytes
SHA256(Wireshark 3.6.13 Intel 64.dmg)=b4466d351da679c990fee4ad0fddf8d88a57aa2d182a8e53352791ac1da7f2c0
SHA1(Wireshark 3.6.13 Intel 64.dmg)=9c6d6e2579571916334aa6396541c55d3a953ac9

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