Wireshark · Wireshark-announce: [Wireshark-announce] Wireshark 3.2.18 is now available

[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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


 This is expected to be the final supported version of the 3.2 branch.
 We really mean it this time.

 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-09[5] Bluetooth SDP dissector crash. Issue
       17635[6]. CVE-2021-39925[7].

     • wnpa-sec-2021-10[8] Bluetooth DHT dissector large loop. Issue
       17677[9]. CVE-2021-39924[10].

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

     • wnpa-sec-2021-12[13] C12.22 dissector crash. Issue 17636[14].
       CVE-2021-39922[15].

     • wnpa-sec-2021-13[16] IEEE 802.11 dissector crash. Issue
       17704[17]. CVE-2021-39928[18].

     • wnpa-sec-2021-14[19] Modbus dissector crash. Issue 17703[20].
       CVE-2021-39921[21].

   The following bugs have been fixed:

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

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

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

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

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

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

  New and Updated Features

   There are no new features in this release.

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   BT SDP, BT-DHT, C12.22, CAN FD, CSN1, EAPOL-MKA, EVS, GSM BSSMAP LE,
   IEEE 802.11, PNRP, TCP, and TLS

  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 2021-11-17 18:34:35 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-09
   6. https://gitlab.com/wireshark/wireshark/-/issues/17635
   7. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39925
   8. https://www.wireshark.org/security/wnpa-sec-2021-10
   9. https://gitlab.com/wireshark/wireshark/-/issues/17677
  10. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39924
  11. https://www.wireshark.org/security/wnpa-sec-2021-11
  12. https://gitlab.com/wireshark/wireshark/-/issues/17684
  13. https://www.wireshark.org/security/wnpa-sec-2021-12
  14. https://gitlab.com/wireshark/wireshark/-/issues/17636
  15. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39922
  16. https://www.wireshark.org/security/wnpa-sec-2021-13
  17. https://gitlab.com/wireshark/wireshark/-/issues/17704
  18. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39928
  19. https://www.wireshark.org/security/wnpa-sec-2021-14
  20. https://gitlab.com/wireshark/wireshark/-/issues/17703
  21. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39921
  22. https://gitlab.com/wireshark/wireshark/-/issues/16525
  23. https://gitlab.com/wireshark/wireshark/-/issues/17089
  24. https://gitlab.com/wireshark/wireshark/-/issues/17623
  25. https://gitlab.com/wireshark/wireshark/-/issues/17654
  26. https://gitlab.com/wireshark/wireshark/-/issues/17667
  27. https://gitlab.com/wireshark/wireshark/-/issues/17722
  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.2.18.tar.xz: 31554816 bytes
SHA256(wireshark-3.2.18.tar.xz)=bbe75d909b052fcd67a850f149f0d5b1e2531026fc2413946b48570293306887
RIPEMD160(wireshark-3.2.18.tar.xz)=4f274e5d2172c84c00333e890d1952eb63f3a5ba
SHA1(wireshark-3.2.18.tar.xz)=92a32d54d80b6068fb75ad41142cec7638b1270a

Wireshark-win64-3.2.18.exe: 70472640 bytes
SHA256(Wireshark-win64-3.2.18.exe)=cbee6bb8d250287d8bcc41dc0353c425d87dceffa5005b3d9ab755090709e7b9
RIPEMD160(Wireshark-win64-3.2.18.exe)=22744e0b5e9779b1f5c184063bd42fcd364e584f
SHA1(Wireshark-win64-3.2.18.exe)=828a3ec890b1f4f01e5c006406c0391507cfce68

Wireshark-win32-3.2.18.exe: 54419544 bytes
SHA256(Wireshark-win32-3.2.18.exe)=a695378bc8b4e1391276efd25038273e11f07427a11288801bebb5c27b6cb3bd
RIPEMD160(Wireshark-win32-3.2.18.exe)=44de0d7c1f4d1745d96e0b6b440d7ad3ba52e299
SHA1(Wireshark-win32-3.2.18.exe)=33d69b99ed2242f691d7a43aad830e8d83318366

Wireshark-win32-3.2.18.msi: 42774528 bytes
SHA256(Wireshark-win32-3.2.18.msi)=9d82986923d0b8411ef9b8143d735da4995f2d134872206c51cf9a4fb71feccb
RIPEMD160(Wireshark-win32-3.2.18.msi)=fb5b4f7d33710657f61a865c5ce2ed9dcab312ac
SHA1(Wireshark-win32-3.2.18.msi)=6e4447a88f48030cc969e41b7ddac2f4b42bc72c

Wireshark-win64-3.2.18.msi: 48066560 bytes
SHA256(Wireshark-win64-3.2.18.msi)=8d72b7e3d9dfaf713eb2db172b9462f29707bf7decda54ced22cd3c5f180f070
RIPEMD160(Wireshark-win64-3.2.18.msi)=2ebaccf8ec19005ac2f7e5feef5ef73804778751
SHA1(Wireshark-win64-3.2.18.msi)=8c7cbfc845d3d41054cc21fc27a3fe696038d18c

WiresharkPortable_3.2.18.paf.exe: 37206504 bytes
SHA256(WiresharkPortable_3.2.18.paf.exe)=c2411b09be9b632f9c344ed62b7fafb8ed464d91f2b8bb0ae2a73c1005559110
RIPEMD160(WiresharkPortable_3.2.18.paf.exe)=34cb1bcbe40b75c70da253be6e4f8b2d01910afd
SHA1(WiresharkPortable_3.2.18.paf.exe)=9c15e35ba4e264ce54fa425c6419ff9c177fe5fd

Wireshark 3.2.18 Intel 64.dmg: 100517488 bytes
SHA256(Wireshark 3.2.18 Intel 64.dmg)=2d53faa508b73e264e10df4cdb0fc66e6c2b0ccf51cb27a78d3edbe2dcf34c37
RIPEMD160(Wireshark 3.2.18 Intel 64.dmg)=62bc44ccaeaa3b04c3669c6c81b43967a5e16e75
SHA1(Wireshark 3.2.18 Intel 64.dmg)=20362363e34385cd7c123883b96242cf2e4993ea

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