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

[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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


 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

  We do not ship official 32-bit Windows packages for Wireshark 4.0 and
  later. If you need to use Wireshark on that platform, we recommend
  using the latest 3.6 release. 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-27[3] RTPS dissector memory leak. Issue 19322[4].
       CVE-2023-5371[5].

   The following bugs have been fixed:

     • Updating from within Wireshark if a file is open fails because it
       can’t close Wireshark. Issue 17658[6].

     • ESL timestamp provided by ET2000 not displayed. Issue 18308[7].

     • Kafka: dissect_kafka_sync_group_request missing version check for
       instance_id. Issue 19290[8].

     • Start Capture via context menu crashes on macOS with an older Qt
       version. Issue 19299[9].

     • Delta time displayed is incorrect after unsetting time reference.
       Issue 19324[10].

     • Fuzz job crash output: randpkt-2023-09-09-7060.pcap. Issue
       19332[11].

     • Missing one bit in SCCP::sequencing/segmenting. Issue 19336[12].

     • Protobuf field malformed packet for last byte of 'repeated
       fixed32' Issue 19342[13].

     • RTP/RFC 4571: Wrong desegmentation/reassembly in RTP over TCP
       packets. Issue 19345[14].

     • Sparklines not working on macOS Sonoma with both native OS and
       Homebrew pcap. Issue 19349[15].

     • Incorrect bit values and namings in BSS Configuration Report TLV.
       Issue 19352[16].

  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

   ESL, GNW, IDN, IEEE 1722, IEEE 1905.1a, ITS, Kafka, ProtoBuf, RTP,
   RTPS, SCCP, TACACS, and Tibia

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

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

  You can learn protocol analysis and meet Wireshark’s developers at
  SharkFest[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-27
   4. https://gitlab.com/wireshark/wireshark/-/issues/19322
   5. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-5371
   6. https://gitlab.com/wireshark/wireshark/-/issues/17658
   7. https://gitlab.com/wireshark/wireshark/-/issues/18308
   8. https://gitlab.com/wireshark/wireshark/-/issues/19290
   9. https://gitlab.com/wireshark/wireshark/-/issues/19299
  10. https://gitlab.com/wireshark/wireshark/-/issues/19324
  11. https://gitlab.com/wireshark/wireshark/-/issues/19332
  12. https://gitlab.com/wireshark/wireshark/-/issues/19336
  13. https://gitlab.com/wireshark/wireshark/-/issues/19342
  14. https://gitlab.com/wireshark/wireshark/-/issues/19345
  15. https://gitlab.com/wireshark/wireshark/-/issues/19349
  16. https://gitlab.com/wireshark/wireshark/-/issues/19352
  17. https://www.wireshark.org/download.html
  18. https://ask.wireshark.org/
  19. https://www.wireshark.org/lists/
  20. https://gitlab.com/wireshark/wireshark/-/issues
  21. https://sharkfest.wireshark.org
  22. https://wiresharkfoundation.org
  23. https://www.wireshark.org/faq.html


Digests

wireshark-4.0.9.tar.xz: 43130608 bytes
SHA256(wireshark-4.0.9.tar.xz)=f96c432098c3602140be3acd56f45c349d7f2c9ada9a309703bf70eda6f5560c
SHA1(wireshark-4.0.9.tar.xz)=64b52d6de6133636388fc993cdc42b87eba898a7

Wireshark-win64-4.0.9.exe: 79152832 bytes
SHA256(Wireshark-win64-4.0.9.exe)=52b10bc3b0864065c3147b171cd9dc276bee953ce80cad613433cf5db7b266ab
SHA1(Wireshark-win64-4.0.9.exe)=b6bb0ced34a3004647ef27084194bf45b1341290

Wireshark-win64-4.0.9.msi: 53276672 bytes
SHA256(Wireshark-win64-4.0.9.msi)=c981f1a0a33c22cd573403b2703ca7cc97fbc815786945be8c6c5a27f4561969
SHA1(Wireshark-win64-4.0.9.msi)=d346eb136130752ae41193987286fce037da759c

WiresharkPortable64_4.0.9.paf.exe: 45814176 bytes
SHA256(WiresharkPortable64_4.0.9.paf.exe)=9d1a0bdf7a203dd38496253bca7c66e0df14858dcf23104920fc7fa40910a91b
SHA1(WiresharkPortable64_4.0.9.paf.exe)=1d1c8b0dbdf87053367f6c14821740a24bea37e5

Wireshark 4.0.9 Arm 64.dmg: 63403102 bytes
SHA256(Wireshark 4.0.9 Arm 64.dmg)=43e40b35d64dbe4209dace980746354e0a3e7044f78e287e32f070b09788d309
SHA1(Wireshark 4.0.9 Arm 64.dmg)=1ea3452bbedd8d8b182220ec6a21ea6e0d9cc985

Wireshark 4.0.9 Intel 64.dmg: 66927572 bytes
SHA256(Wireshark 4.0.9 Intel 64.dmg)=2b936e6e595b99eee22bb61891c243a1fcde14eaf3404e2e6bb18af2d7a6ddf7
SHA1(Wireshark 4.0.9 Intel 64.dmg)=86e19120e42ff7e376dbc1ecebc4c823bdec4798

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