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.10 is now available

From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 17 Nov 2021 12:01:07 -0800
I'm proud to announce the release of Wireshark 3.4.10.


 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

  This release fixes a forward compatibility issue[1] with the I/O
  Graphs preferences.

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2021-07[2] Bluetooth DHT dissector crash. Issue
       17651[3]. CVE-2021-39929[4].

     • wnpa-sec-2021-08[5] Bluetooth HCI_ISO dissector crash. Issue
       17649[6]. CVE-2021-39926[7].

     • wnpa-sec-2021-09[8] Bluetooth SDP dissector crash. Issue
       17635[9]. CVE-2021-39925[10].

     • wnpa-sec-2021-10[11] Bluetooth DHT dissector large loop. Issue
       17677[12]. CVE-2021-39924[13].

     • wnpa-sec-2021-11[14] PNRP dissector large loop. Issue 17684[15].

     • wnpa-sec-2021-12[16] C12.22 dissector crash. Issue 17636[17].
       CVE-2021-39922[18].

     • wnpa-sec-2021-13[19] IEEE 802.11 dissector crash. Issue
       17704[20]. CVE-2021-39928[21].

     • wnpa-sec-2021-14[22] Modbus dissector crash. Issue 17703[23].
       CVE-2021-39921[24].

     • wnpa-sec-2021-15[25] IPPUSB dissector crash. Issue 17705[26].
       CVE-2021-39920[27].

   The following bugs have been fixed:

     • OSS-Fuzz: Heap-use-after-free in ROS Issue 16342[28].

     • Allow for '\0' (NULL) character as filter instead of requiring
       0x00 for the character match Issue 16525[29].

     • Dumpcap with threads reports double received count vs captured
       Issue 17089[30].

     • I/O Graphs values reset to default with 3.5 due to change of UAT
       Issue 17623[31].

     • HTTP2 dissector reports an assertion error on large data frames
       Issue 17633[32].

     • TShark stops capturing when capturing with multiple files and
       packet printing enabled Issue 17654[33].

     • Wireshark is unable to decode the IMSI IE received in BSSMAP
       Perform Location request Issue 17667[34].

     • WSLUA: Crash on reload if Proto has no fields Issue 17668[35].

     • Crash in flow analysis for TCP Issue 17722[36].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   BT HCI_ISO, BT SDP, BT-DHT, C12.22, CAN FD, CSN1, EAPOL-MKA, EVS, GSM
   BSSMAP LE, HTTP2, IDMP, IEEE 1905.1a, IEEE 802.11, IPPUSB, Modbus,
   PNRP, and TCP

  New and Updated Capture File Support

   pcap

 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[37] 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[38] 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[39].

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

 Frequently Asked Questions

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

  Last updated 2021-11-17 17:47:32 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17623
   2. https://www.wireshark.org/security/wnpa-sec-2021-07
   3. https://gitlab.com/wireshark/wireshark/-/issues/17651
   4. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39929
   5. https://www.wireshark.org/security/wnpa-sec-2021-08
   6. https://gitlab.com/wireshark/wireshark/-/issues/17649
   7. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39926
   8. https://www.wireshark.org/security/wnpa-sec-2021-09
   9. https://gitlab.com/wireshark/wireshark/-/issues/17635
  10. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39925
  11. https://www.wireshark.org/security/wnpa-sec-2021-10
  12. https://gitlab.com/wireshark/wireshark/-/issues/17677
  13. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39924
  14. https://www.wireshark.org/security/wnpa-sec-2021-11
  15. https://gitlab.com/wireshark/wireshark/-/issues/17684
  16. https://www.wireshark.org/security/wnpa-sec-2021-12
  17. https://gitlab.com/wireshark/wireshark/-/issues/17636
  18. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39922
  19. https://www.wireshark.org/security/wnpa-sec-2021-13
  20. https://gitlab.com/wireshark/wireshark/-/issues/17704
  21. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39928
  22. https://www.wireshark.org/security/wnpa-sec-2021-14
  23. https://gitlab.com/wireshark/wireshark/-/issues/17703
  24. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39921
  25. https://www.wireshark.org/security/wnpa-sec-2021-15
  26. https://gitlab.com/wireshark/wireshark/-/issues/17705
  27. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39920
  28. https://gitlab.com/wireshark/wireshark/-/issues/16342
  29. https://gitlab.com/wireshark/wireshark/-/issues/16525
  30. https://gitlab.com/wireshark/wireshark/-/issues/17089
  31. https://gitlab.com/wireshark/wireshark/-/issues/17623
  32. https://gitlab.com/wireshark/wireshark/-/issues/17633
  33. https://gitlab.com/wireshark/wireshark/-/issues/17654
  34. https://gitlab.com/wireshark/wireshark/-/issues/17667
  35. https://gitlab.com/wireshark/wireshark/-/issues/17668
  36. https://gitlab.com/wireshark/wireshark/-/issues/17722
  37. https://www.wireshark.org/download.html#thirdparty
  38. https://ask.wireshark.org/
  39. https://www.wireshark.org/lists/
  40. https://gitlab.com/wireshark/wireshark/-/issues
  41. https://www.wireshark.org/faq.html


Digests

wireshark-3.4.10.tar.xz: 32344804 bytes
SHA256(wireshark-3.4.10.tar.xz)=8aa7ef4a44ae62bb8db463cf761e2cc03b97305e0e77ed5be53fa83729187cef
RIPEMD160(wireshark-3.4.10.tar.xz)=eef58ec4e28c6eecc382c1f000257ab60ee6c40c
SHA1(wireshark-3.4.10.tar.xz)=63839abd94d3ae376f860e2d2969777680106578

Wireshark-win64-3.4.10.exe: 71382832 bytes
SHA256(Wireshark-win64-3.4.10.exe)=faa83ac4f289d07d8e1bacb7e7611758b231a9c00b18e816654f40e7437529fd
RIPEMD160(Wireshark-win64-3.4.10.exe)=63068a04839ff02828a6915fe648da25cdeadc84
SHA1(Wireshark-win64-3.4.10.exe)=00c419e3382d24289cfc9d74be6f37934b784066

Wireshark-win32-3.4.10.exe: 55424616 bytes
SHA256(Wireshark-win32-3.4.10.exe)=3bceac74d2d7c388e01b6c25b20088c234fefbcd83e3c960b3e0fcc1eca7839d
RIPEMD160(Wireshark-win32-3.4.10.exe)=84acc6b49f1e8735ec53127b1d9de14a1d121b2f
SHA1(Wireshark-win32-3.4.10.exe)=d6486f9015e60e633f0f2a7fd5152959c4bb749b

Wireshark-win64-3.4.10.msi: 49291264 bytes
SHA256(Wireshark-win64-3.4.10.msi)=b31288207b23700931ddb83785bcc9a9a775758029fbc1cdd653f65b8d802e7d
RIPEMD160(Wireshark-win64-3.4.10.msi)=d93a0cfebe7c2e412ade6e25c3a225b643d498e0
SHA1(Wireshark-win64-3.4.10.msi)=e36624c35824966255f768dc74148a7fe4a895d2

Wireshark-win32-3.4.10.msi: 43925504 bytes
SHA256(Wireshark-win32-3.4.10.msi)=6b6770e596968fdb0e68af3e3dba77631004f374accda085dc59df799011fa0f
RIPEMD160(Wireshark-win32-3.4.10.msi)=374b51b4934bd5d98023df4b8be355bf2c1515e9
SHA1(Wireshark-win32-3.4.10.msi)=df8a5c168bad317ff7b6ed1f12dec4926a2983f2

WiresharkPortable_3.4.10.paf.exe: 38220424 bytes
SHA256(WiresharkPortable_3.4.10.paf.exe)=85f2382b854be81ee7bc3deedaab41214e60e17a83c25822d4e5831c1d88e379
RIPEMD160(WiresharkPortable_3.4.10.paf.exe)=644f056554925fc37a44cfb247d0678efcb01c81
SHA1(WiresharkPortable_3.4.10.paf.exe)=8b36a16b9b602a1f5bb8cc37453fd1678e8fa476

Wireshark 3.4.10 Intel 64.dmg: 131298336 bytes
SHA256(Wireshark 3.4.10 Intel 64.dmg)=1267edf27870fe17e504f2377f78eb7510c4a13e4b53b9b00e171303208749c4
RIPEMD160(Wireshark 3.4.10 Intel 64.dmg)=880a76731ddaed630bfc575e36627cad1e239249
SHA1(Wireshark 3.4.10 Intel 64.dmg)=8783733e2f6f124c102b51f2e245d9deab11ff6d

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