Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

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

Date Prev · Date Next · Thread Prev · Thread Next
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Thu, 10 Feb 2022 12:06:33 -0800
I'm proud to announce the release of Wireshark 3.4.12.


 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-2021-22[1] Kafka dissector infinite loop. Issue
       17811[2].

     • wnpa-sec-2022-01[3] RTMPT dissector infinite loop. Issue
       17813[4].

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

     • wnpa-sec-2022-03[16] PVFS dissector crash. Issue 17840[17].

     • wnpa-sec-2022-04[18] CSN.1 dissector crash. Issue 17882[19].

     • wnpa-sec-2022-05[20] CMS dissector crash. Issue 17935[21].

   The following bugs have been fixed:

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

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

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

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

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

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

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

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

  New and Updated Capture File Support

   There is no new or updated capture file 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[28] 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 About → 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[29] 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[30].

  Issues and feature requests can be reported on the issue tracker[31].

 Frequently Asked Questions

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

  Last updated 2022-02-10 18:45:05 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2021-22
   2. https://gitlab.com/wireshark/wireshark/-/issues/17811
   3. https://www.wireshark.org/security/wnpa-sec-2022-01
   4. https://gitlab.com/wireshark/wireshark/-/issues/17813
   5. https://www.wireshark.org/security/wnpa-sec-2022-02
   6. https://gitlab.com/wireshark/wireshark/-/issues/17829
   7. https://gitlab.com/wireshark/wireshark/-/issues/17842
   8. https://gitlab.com/wireshark/wireshark/-/issues/17847
   9. https://gitlab.com/wireshark/wireshark/-/issues/17855
  10. https://gitlab.com/wireshark/wireshark/-/issues/17891
  11. https://gitlab.com/wireshark/wireshark/-/issues/17925
  12. https://gitlab.com/wireshark/wireshark/-/issues/17926
  13. https://gitlab.com/wireshark/wireshark/-/issues/17931
  14. https://gitlab.com/wireshark/wireshark/-/issues/17932
  15. https://gitlab.com/wireshark/wireshark/-/issues/17933
  16. https://www.wireshark.org/security/wnpa-sec-2022-03
  17. https://gitlab.com/wireshark/wireshark/-/issues/17840
  18. https://www.wireshark.org/security/wnpa-sec-2022-04
  19. https://gitlab.com/wireshark/wireshark/-/issues/17882
  20. https://www.wireshark.org/security/wnpa-sec-2022-05
  21. https://gitlab.com/wireshark/wireshark/-/issues/17935
  22. https://gitlab.com/wireshark/wireshark/-/issues/17784
  23. https://gitlab.com/wireshark/wireshark/-/issues/17834
  24. https://gitlab.com/wireshark/wireshark/-/issues/17868
  25. https://gitlab.com/wireshark/wireshark/-/issues/17878
  26. https://gitlab.com/wireshark/wireshark/-/issues/17886
  27. https://gitlab.com/wireshark/wireshark/-/issues/17909
  28. https://www.wireshark.org/download.html#thirdparty
  29. https://ask.wireshark.org/
  30. https://www.wireshark.org/lists/
  31. https://gitlab.com/wireshark/wireshark/-/issues
  32. https://www.wireshark.org/faq.html


Digests

wireshark-3.4.12.tar.xz: 32373300 bytes
SHA256(wireshark-3.4.12.tar.xz)=881a13303e263b7dc7fe337534c8a541d4914552287879bed30bbe76c5bf68ca
RIPEMD160(wireshark-3.4.12.tar.xz)=aae23d4a583e8d848ae217b7687bb6c7f565384a
SHA1(wireshark-3.4.12.tar.xz)=91ca69b0029e58b9c824266237ab392a62f0a248

Wireshark-win32-3.4.12.exe: 55558872 bytes
SHA256(Wireshark-win32-3.4.12.exe)=00fd3f9a31ff13fb897024f86303fbe4d8086e2760a3aef472c8a36bfadbb6c1
RIPEMD160(Wireshark-win32-3.4.12.exe)=61818bca72bfa4738b9a1b99d9e46b43d2808bdd
SHA1(Wireshark-win32-3.4.12.exe)=0eb43c41a7b740817c48ec82f1afa875d1087c81

Wireshark-win64-3.4.12.exe: 71589160 bytes
SHA256(Wireshark-win64-3.4.12.exe)=e1388be52703df5414d102192336971e78d9283623a07715e7f2d85a470286a7
RIPEMD160(Wireshark-win64-3.4.12.exe)=62344590eff17cccaabde56e3c2109fc664bb6f9
SHA1(Wireshark-win64-3.4.12.exe)=51e12478b58224f327fc13485bc6972df58b315f

Wireshark-win32-3.4.12.msi: 44171264 bytes
SHA256(Wireshark-win32-3.4.12.msi)=7f1b2b1bb6184dcea89c88740b8c785676133b40abd279a572106329fdba2e89
RIPEMD160(Wireshark-win32-3.4.12.msi)=83b51628ba1e26806c3b9364d864fdb0bf72a8fc
SHA1(Wireshark-win32-3.4.12.msi)=1635035552b0597738788361c6d771acdb37c774

Wireshark-win64-3.4.12.msi: 49336320 bytes
SHA256(Wireshark-win64-3.4.12.msi)=4af47b72b0363235f66d2299b55f791db51dcf25634211c3a6b69d362cb1690d
RIPEMD160(Wireshark-win64-3.4.12.msi)=a8ec9022c43bf8c32a25e486f2829590511cb6c8
SHA1(Wireshark-win64-3.4.12.msi)=fd69b177c06ff5dec9c0106411f2f066a12ab678

WiresharkPortable_3.4.12.paf.exe: 38428000 bytes
SHA256(WiresharkPortable_3.4.12.paf.exe)=9c8f2bea3b6b878e1fac98155bfb0b92f16681ee697dc63ec96938febef6ca91
RIPEMD160(WiresharkPortable_3.4.12.paf.exe)=5746656ed48209f83af5406c63daf2e5c7b29e0c
SHA1(WiresharkPortable_3.4.12.paf.exe)=8c475de41889f083969431e0cb254fbb89625f58

Wireshark 3.4.12 Intel 64.dmg: 131377077 bytes
SHA256(Wireshark 3.4.12 Intel 64.dmg)=3d0cca97ef53cf142747ac31a2a9cad57025f873daac320c1b3120c4d92cc588
RIPEMD160(Wireshark 3.4.12 Intel 64.dmg)=04fea8ebf766676da18b1582ed565a8ba8f6a21b
SHA1(Wireshark 3.4.12 Intel 64.dmg)=7c635cee95009e4f3a1ca515a504f28308cc867f

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