[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2022-01[1] RTMPT dissector infinite loop. Issue
       17813[2].

     • wnpa-sec-2022-02[3] Large loops in multiple dissectors. Issue
       17829[4], Issue 17842[5], Issue 17847[6], Issue 17855[7], Issue
       17891[8], Issue 17925[9], Issue 17926[10], Issue 17931[11], Issue
       17932[12], Issue 17933[13].

     • wnpa-sec-2022-03[14] PVFS dissector crash. Issue 17840[15].

     • wnpa-sec-2022-04[16] CSN.1 dissector crash. Issue 17882[17].

     • wnpa-sec-2022-05[18] CMS dissector crash. Issue 17935[19].

   The following bugs have been fixed:

     • Support for GSM SMS TPDU in HTTP2 body Issue 17784[20].

     • Wireshark 3.6.1 broke the ABI by removing ws_log_default_writer
       from libwsutil Issue 17822[21].

     • Fedora RPM package build failing with RPATH of /usr/local/lib64
       Issue 17830[22].

     • macos-setup.sh: ftp.pcre.org no longer exists Issue 17834[23].

     • nmap.org/npcap → npcap.com: domain/URL change Issue 17838[24].

     • MPLS ECHO FEC stack change TLV not dissected correctly Issue
       17868[25].

     • Attempting to open a systemd journal export file segfaults Issue
       17875[26].

     • Dissector bug on 802.11ac packets Issue 17878[27].

     • The Info column shows only one NGAP/S1AP packet of several
       packets inside an SCTP packet Issue 17886[28].

     • Uninstalling Wireshark 3.6.1 on Windows 10 fails to remove the
       installation directory because it doesn’t remove the User’s Guide
       subdirectory and all its contents. Issue 17898[29].

     • 3.6 doesn’t build without zlib Issue 17899[30].

     • SIP Statistics no longer properly reporting method type
       accounting Issue 17904[31].

     • Fuzz job crash output: fuzz-2022-01-26-6940.pcap Issue 17909[32].

     • SCTP retransmission detection broken for the first data chunk of
       each association with relative TSN Issue 17917[33].

     • “Show In Folder” doesn’t work correctly for filenames with spaces
       Issue 17927[34].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   AMP, ASN.1 PER, ATN-ULCS, BGP, BP, CFLOW, CMS, CSN.1, GDSDB, GSM RP,
   GTP, HTTP3, IEEE 802.11 Radiotap, IPDC, ISAKMP, Kafka, MP2T, MPEG
   PES, MPEG SECT, MPLS ECHO, NGAP, NTLMSSP, OpenFlow 1.4, OpenFlow 1.5,
   P_MUL, PN-RT, PROXY, PTP, PVFS, RSL, RTMPT, rtnetlink, S1AP, SCTP,
   Signal PDU, SIP, TDS, USB, WAP, and ZigBee ZCL

  New and Updated Capture File Support

   BLF and libpcap

  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[35] 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[36] 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[37].

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

 Frequently Asked Questions

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

  Last updated 2022-02-10 18:32:36 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2022-01
   2. https://gitlab.com/wireshark/wireshark/-/issues/17813
   3. https://www.wireshark.org/security/wnpa-sec-2022-02
   4. https://gitlab.com/wireshark/wireshark/-/issues/17829
   5. https://gitlab.com/wireshark/wireshark/-/issues/17842
   6. https://gitlab.com/wireshark/wireshark/-/issues/17847
   7. https://gitlab.com/wireshark/wireshark/-/issues/17855
   8. https://gitlab.com/wireshark/wireshark/-/issues/17891
   9. https://gitlab.com/wireshark/wireshark/-/issues/17925
  10. https://gitlab.com/wireshark/wireshark/-/issues/17926
  11. https://gitlab.com/wireshark/wireshark/-/issues/17931
  12. https://gitlab.com/wireshark/wireshark/-/issues/17932
  13. https://gitlab.com/wireshark/wireshark/-/issues/17933
  14. https://www.wireshark.org/security/wnpa-sec-2022-03
  15. https://gitlab.com/wireshark/wireshark/-/issues/17840
  16. https://www.wireshark.org/security/wnpa-sec-2022-04
  17. https://gitlab.com/wireshark/wireshark/-/issues/17882
  18. https://www.wireshark.org/security/wnpa-sec-2022-05
  19. https://gitlab.com/wireshark/wireshark/-/issues/17935
  20. https://gitlab.com/wireshark/wireshark/-/issues/17784
  21. https://gitlab.com/wireshark/wireshark/-/issues/17822
  22. https://gitlab.com/wireshark/wireshark/-/issues/17830
  23. https://gitlab.com/wireshark/wireshark/-/issues/17834
  24. https://gitlab.com/wireshark/wireshark/-/issues/17838
  25. https://gitlab.com/wireshark/wireshark/-/issues/17868
  26. https://gitlab.com/wireshark/wireshark/-/issues/17875
  27. https://gitlab.com/wireshark/wireshark/-/issues/17878
  28. https://gitlab.com/wireshark/wireshark/-/issues/17886
  29. https://gitlab.com/wireshark/wireshark/-/issues/17898
  30. https://gitlab.com/wireshark/wireshark/-/issues/17899
  31. https://gitlab.com/wireshark/wireshark/-/issues/17904
  32. https://gitlab.com/wireshark/wireshark/-/issues/17909
  33. https://gitlab.com/wireshark/wireshark/-/issues/17917
  34. https://gitlab.com/wireshark/wireshark/-/issues/17927
  35. https://www.wireshark.org/download.html
  36. https://ask.wireshark.org/
  37. https://www.wireshark.org/lists/
  38. https://gitlab.com/wireshark/wireshark/-/issues
  39. https://www.wireshark.org/faq.html


Digests

wireshark-3.6.2.tar.xz: 39654296 bytes
SHA256(wireshark-3.6.2.tar.xz)=5d901a5572aef953f04adc253ed2a0699d4c62779d3249021e1e8541a024c30e
RIPEMD160(wireshark-3.6.2.tar.xz)=da465f279204f8913b9dcb76043b8162b60ed40d
SHA1(wireshark-3.6.2.tar.xz)=d4cf3da54021a763e0bf5f28b4f0bf5c0912d344

Wireshark-win64-3.6.2.exe: 77465592 bytes
SHA256(Wireshark-win64-3.6.2.exe)=8b02c49d60e1e5261fe95ad27e5f5f3ae81990332dd2621959daad7ba84e5388
RIPEMD160(Wireshark-win64-3.6.2.exe)=18355d12b844ebc5cdee1a6b84aff237483d8387
SHA1(Wireshark-win64-3.6.2.exe)=7343c59e1d70f77a370155873b83208ae1908bc6

Wireshark-win32-3.6.2.exe: 61320568 bytes
SHA256(Wireshark-win32-3.6.2.exe)=8b0f9f2bad9e9fe30a78c9221eb81bda7da94bf65b1994bb28ebe2586a9e8408
RIPEMD160(Wireshark-win32-3.6.2.exe)=8685fa838b0506dbb320ae26455ece427abd1ee0
SHA1(Wireshark-win32-3.6.2.exe)=8e509a6df3e12b702d363c3d634445c25e6767f5

Wireshark-win32-3.6.2.msi: 45486080 bytes
SHA256(Wireshark-win32-3.6.2.msi)=dd23322a8767482f6b7c37cf27d3c977abdca80362e1ba8e4454c1c0f279967d
RIPEMD160(Wireshark-win32-3.6.2.msi)=9385476553c225bb8782ec5bc446ba0cd20f8f67
SHA1(Wireshark-win32-3.6.2.msi)=787d590c2ddcefad3e4acd33948461609e103122

Wireshark-win64-3.6.2.msi: 50790400 bytes
SHA256(Wireshark-win64-3.6.2.msi)=62f1e4540b1dce852d83030c4ca28c7566facce2811f970d5bd77be858d253e2
RIPEMD160(Wireshark-win64-3.6.2.msi)=238d5854f2c438b514d189bd95cfaa3c94a9666a
SHA1(Wireshark-win64-3.6.2.msi)=0bcd2a4b47762a5d6ecc532bcba60d3bc714dbac

WiresharkPortable64_3.6.2.paf.exe: 44287624 bytes
SHA256(WiresharkPortable64_3.6.2.paf.exe)=7d82830495f3e44adae80bab9e31546d1db2b20f1a15eff8114734c8bb5138f8
RIPEMD160(WiresharkPortable64_3.6.2.paf.exe)=b552499b4cc52b8af4fb9e71d9d68bfd37c3eaf8
SHA1(WiresharkPortable64_3.6.2.paf.exe)=b9d5c55c236db415d623772dfe10ac4576c58302

WiresharkPortable32_3.6.2.paf.exe: 39538544 bytes
SHA256(WiresharkPortable32_3.6.2.paf.exe)=7d173ef36556a820649e37ff4783c8fdfaa57efe01dd77a9f71481db9c4ff092
RIPEMD160(WiresharkPortable32_3.6.2.paf.exe)=7a7da1b6fa647ce8927c6913bda90e50ab9bfc94
SHA1(WiresharkPortable32_3.6.2.paf.exe)=16ed9196cfc0ec3b6a98adbea958516bd458b9ad

Wireshark 3.6.2 Arm 64.dmg: 139809400 bytes
SHA256(Wireshark 3.6.2 Arm 64.dmg)=3835b6942192675ed3173c4f5fa2bf144c5f6792b3624b140ab9525ca362b17e
RIPEMD160(Wireshark 3.6.2 Arm 64.dmg)=edae2e33a5875a084f784a25bc4def35b20e9452
SHA1(Wireshark 3.6.2 Arm 64.dmg)=ff59c2bf0825a072d9ec7057db1dd0851994eb0e

Wireshark 3.6.2 Intel 64.dmg: 138770043 bytes
SHA256(Wireshark 3.6.2 Intel 64.dmg)=7d434803ca73a4282b1e52b77510d176063b609eda98dfa3ddb30c963cf616e3
RIPEMD160(Wireshark 3.6.2 Intel 64.dmg)=858d58b33c154dcecc3433038bf02266546bdd74
SHA1(Wireshark 3.6.2 Intel 64.dmg)=a36c317cc927a2d596b3d1efe59632300de8704b

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