Wireshark-users: [Wireshark-users] Wireshark 4.0.8 is now available

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 23 Aug 2023 13:38:47 -0700
I'm proud to announce the release of Wireshark 4.0.8.


 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-23[3] CBOR dissector crash. Issue 19144[4].

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

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

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

   The following bugs have been fixed:

     • TShark cannot capture to pipe on Windows correctly. Issue
       17900[11].

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

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

     • RTP Player only shows waveform until sequence rollover. Issue
       18829[14].

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

     • Crash on DICOM Export Objects window close. Issue 19207[16].

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

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

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

     • Websocket packets not decoded and displayed for Field type=Custom
       and Field name websocket.payload.text. Issue 19220[20].

     • Cannot read pcapng file captured on OpenBSD and read on FreeBSD.
       Issue 19230[21].

     • UI: While capturing the Wireshark icon changes from green to blue
       when new file is created. Issue 19252[22].

     • Conversation: heap-use-after-free after wmem_leave_file_scope.
       Issue 19265[23].

     • IP Packets with DSCP 44 does not indicate "Voice-Admit" Issue
       19270[24].

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

     • UI: Auto scroll button in the toolbar is turned on when manually
       scrolling to the end of packet list. Issue 19274[26].

  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, CBOR, CFM, CP2179, CQL, DHCPFO, DICOM, F1AP, GSM DTAP, IEEE
   802.11, IPv4, NAS-5GS, PFCP, PKT CCC, QUIC, RTP, TFTP, WebSocket, and
   XnAP

  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[27] 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[28] 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[29].

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

  You can learn protocol analysis and meet Wireshark’s developers at
  SharkFest[31].

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

 Frequently Asked Questions

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

 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-23
   4. https://gitlab.com/wireshark/wireshark/-/issues/19144
   5. https://www.wireshark.org/security/wnpa-sec-2023-24
   6. https://gitlab.com/wireshark/wireshark/-/issues/19258
   7. https://www.wireshark.org/security/wnpa-sec-2023-25
   8. https://gitlab.com/wireshark/wireshark/-/issues/19259
   9. https://www.wireshark.org/security/wnpa-sec-2023-26
  10. https://gitlab.com/wireshark/wireshark/-/issues/19229
  11. https://gitlab.com/wireshark/wireshark/-/issues/17900
  12. https://gitlab.com/wireshark/wireshark/-/issues/18279
  13. https://gitlab.com/wireshark/wireshark/-/issues/18326
  14. https://gitlab.com/wireshark/wireshark/-/issues/18829
  15. https://gitlab.com/wireshark/wireshark/-/issues/19198
  16. https://gitlab.com/wireshark/wireshark/-/issues/19207
  17. https://gitlab.com/wireshark/wireshark/-/issues/19209
  18. https://gitlab.com/wireshark/wireshark/-/issues/19213
  19. https://gitlab.com/wireshark/wireshark/-/issues/19216
  20. https://gitlab.com/wireshark/wireshark/-/issues/19220
  21. https://gitlab.com/wireshark/wireshark/-/issues/19230
  22. https://gitlab.com/wireshark/wireshark/-/issues/19252
  23. https://gitlab.com/wireshark/wireshark/-/issues/19265
  24. https://gitlab.com/wireshark/wireshark/-/issues/19270
  25. https://gitlab.com/wireshark/wireshark/-/issues/19273
  26. https://gitlab.com/wireshark/wireshark/-/issues/19274
  27. https://www.wireshark.org/download.html
  28. https://ask.wireshark.org/
  29. https://www.wireshark.org/lists/
  30. https://gitlab.com/wireshark/wireshark/-/issues
  31. https://sharkfest.wireshark.org
  32. https://wiresharkfoundation.org
  33. https://www.wireshark.org/faq.html


Digests

wireshark-4.0.8.tar.xz: 43123664 bytes
SHA256(wireshark-4.0.8.tar.xz)=16663585c0ffefd5593a6628d4a20cc8241b9703b11283cfe71ead2b750888c8
SHA1(wireshark-4.0.8.tar.xz)=8ca1cc4471d0cb835cd5216833c393fa23bc154f

Wireshark-win64-4.0.8.exe: 79164216 bytes
SHA256(Wireshark-win64-4.0.8.exe)=8243e019d2bd73c81de53c67ddb23d877ecec2fc1699c9aa074ccaa2d7d9b267
SHA1(Wireshark-win64-4.0.8.exe)=1b8a7462eeaebf78f5a50897aa769566596325bf

Wireshark-win64-4.0.8.msi: 53239808 bytes
SHA256(Wireshark-win64-4.0.8.msi)=74d4ed6c9ab093fcebdfb034f4a0480c11774bfac72b7b3271cdadc3098278a0
SHA1(Wireshark-win64-4.0.8.msi)=ad3d422dad9cb0b4140abc311ce152c151151fdd

WiresharkPortable64_4.0.8.paf.exe: 45811360 bytes
SHA256(WiresharkPortable64_4.0.8.paf.exe)=5b328b24f12760b99fe36936154e442177668f52300685fe68fdd1ec6871d647
SHA1(WiresharkPortable64_4.0.8.paf.exe)=a6e8c3b40744454bd4461fcfc43c4eddcdcaa044

Wireshark 4.0.8 Arm 64.dmg: 64637754 bytes
SHA256(Wireshark 4.0.8 Arm 64.dmg)=cbf50f162411b4870b07f1460ada76d357dafbd20e5243a97b055ddb39d9fcac
SHA1(Wireshark 4.0.8 Arm 64.dmg)=f4ee4e70f43879fc83237b1b13a5665bc143c6e9

Wireshark 4.0.8 Intel 64.dmg: 68136239 bytes
SHA256(Wireshark 4.0.8 Intel 64.dmg)=a751eb215c0337982675b889bf48e742a57859eaaf3a0f7d64ddc27e6a459595
SHA1(Wireshark 4.0.8 Intel 64.dmg)=8eed4c8a9ed54116d7c717fb3e7a0c4241b2641e

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