Wireshark-announce: [Wireshark-announce] Wireshark 3.2.2 is now available
Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <[email protected]>
Date: Wed, 26 Feb 2020 14:17:57 -0800
I'm proud to announce the release of Wireshark 3.2.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

  Automatic updates were inadvertently disabled in the Wireshark 3.2.1
  64-bit and 32-bit Windows installers. If you’re running Wireshark
  3.2.1 on Windows you will have to update to a later version manually.
  Bug 16381[1]

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2020-03[2] LTE RRC dissector memory leak. Bug 16341[3].

     • wnpa-sec-2020-04[4] WiMax DLMAP dissector crash. Bug 16368[5].

     • wnpa-sec-2020-05[6] EAP dissector crash. Bug 16397[7].

     • wnpa-sec-2020-06[8] WireGuard dissector crash. Bug 16394[9].

   The following bugs have been fixed:

     • Add (IETF) QUIC Dissector. Bug 13881[10].

     • Support for CoAP over TCP and WebSockets (RFC 8323). Bug
       15910[11].

     • SMB IOCTL response packet with BUFFER_OVERFLOW status is
       dissected improperly. Bug 16261[12].

     • Wireshark fails to build with GCC-9. Bug 16319[13].

     • NVMe/TCP ICReq PDU Not Interpreted Correctly. Bug 16333[14].

     • ICMP: No response if ICMP reply packet has an ICMP checksum of
       0x0000. Bug 16334[15].

     • Display filter parsing broken after upgrade from 3.0.7. Bug
       16336[16].

     • IPv4 fragment offset value is incorrect in IPv4 header decode.
       Bug 16344[17].

     • RTCP frame length warning for SAT>IP APP packets. Bug 16345[18].

     • RTP export to rtpdump file doesn’t work. Bug 16351[19].

     • CFDP dissector skips a byte. Bug 16361[20].

     • ISAKMP: IKEv2 transforms and proposal have critical bit (BUG).
       Bug 16364[21].

     • No IPv4/IPv6 hosts in Resolved Addresses dialog. Bug 16366[22].

     • Lack of Check for Updates option in the Windows GUI. Bug
       16381[23].

     • LLDP dissector consumes all octets to the end of the TVB and eth
       trailer dissector does not get called. Bug 16387[24].

     • LACP dissector consumes all octets to the end of the TVB and eth
       trailer dissector does not get called. Bug 16388[25].

  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

   ARTNET, CFDP, CoAP, EAP, GTP, ICMP, ICMPv6, IPv4, ISAKMP, LACP, LLDP,
   LTE RRC, NBAP, NVME-TCP, QUIC, RDM, RTCP, RTP, SMB, SOME/IP, TLS,
   WiMax DLMAP, and WireGuard

  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[26] 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[27] 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[28].

  Bugs and feature requests can be reported on the bug tracker[29].

 Frequently Asked Questions

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

  Last updated 2020-02-26 18:46:23 UTC

 References

   1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16381
   2. https://www.wireshark.org/security/wnpa-sec-2020-03
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16341
   4. https://www.wireshark.org/security/wnpa-sec-2020-04
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16368
   6. https://www.wireshark.org/security/wnpa-sec-2020-05
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16397
   8. https://www.wireshark.org/security/wnpa-sec-2020-06
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16394
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13881
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15910
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16261
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16319
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16333
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16334
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16336
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16344
  18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16345
  19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16351
  20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16361
  21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16364
  22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16366
  23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16381
  24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16387
  25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16388
  26. https://www.wireshark.org/download.html#thirdparty
  27. https://ask.wireshark.org/
  28. https://www.wireshark.org/lists/
  29. https://bugs.wireshark.org/
  30. https://www.wireshark.org/faq.html


Digests

wireshark-3.2.2.tar.xz: 31548392 bytes
SHA256(wireshark-3.2.2.tar.xz)=5f5923ef4c3fee370ed0ca1bb324f37c246015eba4a7e74ab95d9208feeded79
RIPEMD160(wireshark-3.2.2.tar.xz)=886e731f8055c32f82d29931981b13a07bb0584c
SHA1(wireshark-3.2.2.tar.xz)=9cc54a56e9c2ed77e1bc436d9ae2f7bba68d26f8

Wireshark-win64-3.2.2.exe: 60064040 bytes
SHA256(Wireshark-win64-3.2.2.exe)=cc9b49c696219cc093debaae11febeb546b2a508f41150b983ae0af6954c0512
RIPEMD160(Wireshark-win64-3.2.2.exe)=2b292f3882e1eb27a01707fc98aa460501cbb296
SHA1(Wireshark-win64-3.2.2.exe)=865313414ccd9a1f9792f0a94e5de01b59716274

Wireshark-win32-3.2.2.exe: 54766256 bytes
SHA256(Wireshark-win32-3.2.2.exe)=73af61a1edae2af371e432a09bbda8af48a8ada0ea789592ff24499d80070ae6
RIPEMD160(Wireshark-win32-3.2.2.exe)=849d9cbb6c807369148a7e80826b62892ae6d9e6
SHA1(Wireshark-win32-3.2.2.exe)=32cfdad68a57619fad98a36b184fcba9aecd7f40

Wireshark-win64-3.2.2.msi: 48234496 bytes
SHA256(Wireshark-win64-3.2.2.msi)=2be8c75267a4a5670facc7246e3afa145a9f0b04fe9cc6a03876a2100cf54d51
RIPEMD160(Wireshark-win64-3.2.2.msi)=34ce997ebc0f70a5f58ec8c9ad469743ebc7b7a8
SHA1(Wireshark-win64-3.2.2.msi)=c03c345347ff1b2e143bea23521a3e3051dce4ec

Wireshark-win32-3.2.2.msi: 42946560 bytes
SHA256(Wireshark-win32-3.2.2.msi)=9806b8985b5e697b273dd16d5039877b7f7d2bed3c48581f540556cf5b60ee57
RIPEMD160(Wireshark-win32-3.2.2.msi)=9136a45df0d15d526b308697560a3cd3fb8328e4
SHA1(Wireshark-win32-3.2.2.msi)=4730be9ec289cc33b290216de2f42027980de9e9

WiresharkPortable_3.2.2.paf.exe: 36532592 bytes
SHA256(WiresharkPortable_3.2.2.paf.exe)=bcae2ceaf37afb2ab1f6bb1b9f1054c68a537e22b98219407561007ba3217647
RIPEMD160(WiresharkPortable_3.2.2.paf.exe)=d66557ea96adadff42db9b484ab1030da9a92855
SHA1(WiresharkPortable_3.2.2.paf.exe)=1235aaa1a73b33065ebab1e21bdcb2c10a9bbf55

Wireshark 3.2.2 Intel 64.dmg: 97487826 bytes
SHA256(Wireshark 3.2.2 Intel 64.dmg)=c6bda7aba34c441dc8b3998ffbe938ea37a98cf9e4cbf0136a8b65229ce0887f
RIPEMD160(Wireshark 3.2.2 Intel 64.dmg)=db7aaf2ff01d14653c5dbca355cf042cdc472192
SHA1(Wireshark 3.2.2 Intel 64.dmg)=1a37a7cd62ab258431ad166d62cfbc42f0a7287a

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 Intel 64.dmg"
    Other: openssl sha256 wireshark-x.y.z.tar.xz

Attachment: signature.asc
Description: OpenPGP digital signature