[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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


 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]

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2022-09[2] Multiple dissector infinite loops.

     • wnpa-sec-2022-10[3] Kafka dissector memory exhaustion.

   The following bugs have been fixed:

     • Qt: Endpoints dialog - unexpected byte unit suffixes in packet
       columns. Issue 18229[4].

     • GOOSE: field "floating_point" not working anymore. Issue
       18491[5].

     • EVS Header-Full format padding issues. Issue 18498[6].

     • Wireshark 4.0.0 VOIP playback has no sound and can’t resume after
       pausing. Issue 18510[7].

     • Wireshark crashes when exporting a profile on Mac OSX if there is
       no extension. Issue 18525[8].

     • EVS dissector missing value description. Issue 18550[9].

     • Qt 6 font descriptions not backward compatible with Qt 5. Issue
       18553[10].

     • Wireshark, wrong TCP ACKed unseen segment message. Issue
       18558[11].

     • Invalid Cyrillic symbol in timezone at \"Arrival Time\" field in
       frame. Issue 18562[12].

     • ProtoBuf parse extension definitions failed. Issue 18599[13].

     • Fuzz job crash output: fuzz-2022-11-09-11134.pcap. Issue
       18613[14].

     • Fuzz job crash output: fuzz-2022-11-14-11111.pcap. Issue
       18632[15].

     • Wireshark is using old version of ASN (ETSI TS 125 453 V11.2.0)
       which is imapacting length of param in the messages. Issue
       18646[16].

     • BGP: False IGMP flags value in EVPN routes (type 6,7,8) Issue
       18660[17].

     • wslog assumes stderr and stdout exist. Issue 18684[18].

     • Editing packet comments, with non-ASCII characters, on Windows
       saves them in the local code page, not in UTF-8. Issue 18698[19].

     • Unable to decrypt PSK based DTLS traffic which uses Connection
       ID. Issue 18705[20].

     • HTTP2 tests fail when built without nghttp2. Issue 18707[21].

  New and Updated Features

  Removed Features and Support

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   ASN.1 PER, ASTERIX, BGP, BPv6, DTLS, EVS, GOOSE, GSM Osmux, IPv6,
   Kafka, Locamation IM, MONGO, NXP 802.15.4, OpenFlow v6, PCAP,
   Protobuf, RTP, S1AP, SKINNY, TCP, and WASSP

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

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

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

 Frequently Asked Questions

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

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17779
   2. https://www.wireshark.org/security/wnpa-sec-2022-09
   3. https://www.wireshark.org/security/wnpa-sec-2022-10
   4. https://gitlab.com/wireshark/wireshark/-/issues/18229
   5. https://gitlab.com/wireshark/wireshark/-/issues/18491
   6. https://gitlab.com/wireshark/wireshark/-/issues/18498
   7. https://gitlab.com/wireshark/wireshark/-/issues/18510
   8. https://gitlab.com/wireshark/wireshark/-/issues/18525
   9. https://gitlab.com/wireshark/wireshark/-/issues/18550
  10. https://gitlab.com/wireshark/wireshark/-/issues/18553
  11. https://gitlab.com/wireshark/wireshark/-/issues/18558
  12. https://gitlab.com/wireshark/wireshark/-/issues/18562
  13. https://gitlab.com/wireshark/wireshark/-/issues/18599
  14. https://gitlab.com/wireshark/wireshark/-/issues/18613
  15. https://gitlab.com/wireshark/wireshark/-/issues/18632
  16. https://gitlab.com/wireshark/wireshark/-/issues/18646
  17. https://gitlab.com/wireshark/wireshark/-/issues/18660
  18. https://gitlab.com/wireshark/wireshark/-/issues/18684
  19. https://gitlab.com/wireshark/wireshark/-/issues/18698
  20. https://gitlab.com/wireshark/wireshark/-/issues/18705
  21. https://gitlab.com/wireshark/wireshark/-/issues/18707
  22. https://www.wireshark.org/download.html
  23. https://ask.wireshark.org/
  24. https://www.wireshark.org/lists/
  25. https://gitlab.com/wireshark/wireshark/-/issues
  26. https://sharkfest.wireshark.org
  27. https://www.wireshark.org/faq.html


Digests

wireshark-4.0.2.tar.xz: 41296132 bytes
SHA256(wireshark-4.0.2.tar.xz)=f35915699f2f9b28ddb211202d40ec8984e5834d3c911483144a4984ba44411d
SHA1(wireshark-4.0.2.tar.xz)=0127180ff18515b086fe5603f767f53ddaa64c1a

Wireshark-win64-4.0.2.exe: 78713984 bytes
SHA256(Wireshark-win64-4.0.2.exe)=bafc2b00ce557cc531dfbb0e87cda6277c052a32411e10da8005c4001438d8fc
SHA1(Wireshark-win64-4.0.2.exe)=06442fc937533ed61e980847398dd023c1747ea4

Wireshark-win64-4.0.2.msi: 52125696 bytes
SHA256(Wireshark-win64-4.0.2.msi)=ba9fc3b381744362787bfac1df22e63605fd0ba439a8e550a811ca4ba4160579
SHA1(Wireshark-win64-4.0.2.msi)=d2b186ddde175e5d5b646b2592b11fa92392ff8e

WiresharkPortable64_4.0.2.paf.exe: 45467728 bytes
SHA256(WiresharkPortable64_4.0.2.paf.exe)=3aabc8aa09a588334c7964db455d9ce34186775c17adfd703d204f4a6b852923
SHA1(WiresharkPortable64_4.0.2.paf.exe)=b6c9464bc18e9c9629513b9182b640c92a171953

Wireshark 4.0.2 Arm 64.dmg: 62683770 bytes
SHA256(Wireshark 4.0.2 Arm 64.dmg)=3a1d91deb6a40d1834c5e445ee4e92bd6c37eb6791d605d227cd54d6b8951b01
SHA1(Wireshark 4.0.2 Arm 64.dmg)=4940a329012d2cd67ac06de0522bfb6cba9086f2

Wireshark 4.0.2 Intel 64.dmg: 65624548 bytes
SHA256(Wireshark 4.0.2 Intel 64.dmg)=9cc8ca2f48858285d3511f3e5e9167aedcfaebc5c06da8369766a4d2d69aa37e
SHA1(Wireshark 4.0.2 Intel 64.dmg)=845218249010044b4f926a93547aa6085e8b3e94

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