ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-announce: [Wireshark-announce] Wireshark 4.0.11 is now available

From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Wed, 15 Nov 2023 12:54:29 -0800
I'm proud to announce the release of Wireshark 4.0.11.


 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-28[3] SSH dissector crash. Issue 19369[4].

     • wnpa-sec-2023-29[5] NetScreen file parser crash. Issue 19404[6].

   The following bugs have been fixed:

     • First ZigBee APS packet is not decrypted. Issue 16507[7].

     • Problem with decoding OpenFlow actions in OFPT_FLOW_MOD message.
       Issue 17072[8].

     • The "frames" method in sharkd does not consider time references
       and displays incorrect delta time. Issue 17923[9].

     • Wireshark and TShark throw packet-wireguard-WARNING when running
       on systems with FIPS enabled. Issue 18441[10].

     • Wireshark interprets If_fcslen option in the Interface
       Description Block as byte instead of bit. Issue 19174[11].

     • Flathub’s Wireshark page shows wrong version number. Issue
       19382[12].

     • OSPFv3 RI decode error. Issue 19444[13].

     • GSM SIM READ / UPDATE BINARY command has wrong offset. Issue
       19472[14].

  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

   DHCP, GSM SIM, IEEE 1722, ISDN SUP, ISO 15765, OpenFlow v1, OSPF,
   SSH, TCP, TECMP, Wi-SUN, WireGuard, and ZigBee

  New and Updated Capture File Support

   NetScreen and pcapng

  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[15] 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[16] 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[17].

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

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

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

 Frequently Asked Questions

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

 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-28
   4. https://gitlab.com/wireshark/wireshark/-/issues/19369
   5. https://www.wireshark.org/security/wnpa-sec-2023-29
   6. https://gitlab.com/wireshark/wireshark/-/issues/19404
   7. https://gitlab.com/wireshark/wireshark/-/issues/16507
   8. https://gitlab.com/wireshark/wireshark/-/issues/17072
   9. https://gitlab.com/wireshark/wireshark/-/issues/17923
  10. https://gitlab.com/wireshark/wireshark/-/issues/18441
  11. https://gitlab.com/wireshark/wireshark/-/issues/19174
  12. https://gitlab.com/wireshark/wireshark/-/issues/19382
  13. https://gitlab.com/wireshark/wireshark/-/issues/19444
  14. https://gitlab.com/wireshark/wireshark/-/issues/19472
  15. https://www.wireshark.org/download.html
  16. https://ask.wireshark.org/
  17. https://www.wireshark.org/lists/
  18. https://gitlab.com/wireshark/wireshark/-/issues
  19. https://sharkfest.wireshark.org
  20. https://wiresharkfoundation.org
  21. https://www.wireshark.org/faq.html


Digests

wireshark-4.0.11.tar.xz: 43153680 bytes
SHA256(wireshark-4.0.11.tar.xz)=4c341cc33a6c512d983f4126e6f3e5c249f604e14ab7f337d38b1cbe58199e3d
SHA1(wireshark-4.0.11.tar.xz)=4af3140d69f9d41e1c4e161fad66304a6920ddce

Wireshark-win64-4.0.11.exe: 79609384 bytes
SHA256(Wireshark-win64-4.0.11.exe)=f3bb3156ef2c3470d45d4150038c2cc86ae0d04d501ff2c662196eeeaf85d633
SHA1(Wireshark-win64-4.0.11.exe)=24f51cc40b0c404146f5436223ec29c35476c353

Wireshark-win64-4.0.11.msi: 54325248 bytes
SHA256(Wireshark-win64-4.0.11.msi)=b06fab0a8d02788f71a21cf9473c4c38c2d93195b8029825d3de00e9bf199ca9
SHA1(Wireshark-win64-4.0.11.msi)=13eebda94ff1bb39fcd039ca7070e26cf990134a

WiresharkPortable64_4.0.11.paf.exe: 46772200 bytes
SHA256(WiresharkPortable64_4.0.11.paf.exe)=686c04c42fdd101986e664216033d2b5a13911b379ffc93c3546ec354245e998
SHA1(WiresharkPortable64_4.0.11.paf.exe)=cf1417b2fc190a118e5d8711966eaa2521a50a23

Wireshark 4.0.11 Arm 64.dmg: 65048706 bytes
SHA256(Wireshark 4.0.11 Arm 64.dmg)=f8bf18df6c74624c18d79f937c537588f53e1cca5ecfd5d59edbcaa6029ce852
SHA1(Wireshark 4.0.11 Arm 64.dmg)=519322ec6cdc5e9e9831fc62597ee1aff1923550

Wireshark 4.0.11 Intel 64.dmg: 68640199 bytes
SHA256(Wireshark 4.0.11 Intel 64.dmg)=b9a0dc1942c5f78214a986773b22180bba720f51b45e2da4260318b83b504d0d
SHA1(Wireshark 4.0.11 Intel 64.dmg)=8712a3168703935032b828ea69fd1ae12620b20d

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.asc
Description: OpenPGP digital signature