ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-announce: [Wireshark-announce] Wireshark 3.2.6 is now available

Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Wed, 12 Aug 2020 12:50:38 -0700
I'm proud to announce the release of Wireshark 3.2.6.


 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-2020-10[1] Kafka dissector crash. Bug 16672[2].
       CVE-2020-17498[3].

   The following bugs have been fixed:

     • Kafka dissector fails parsing FETCH responses. Bug 16623[4].

     • Dissector for ASTERIX Category 001 / 210 does not recognize bit 1
       as extension. Bug 16662[5].

     • "invalid timestamp" for Systemd Journal Export Block. Bug
       16664[6].

     • Decoding Extended Emergency number list IE length. Bug 16668[7].

     • Some macOS Bluetooth PacketLogger capture files aren’t recognized
       as PacketLogger files (regression, bisected). Bug 16670[8].

     • Short IMSIs (5 digits) lead to wrong decoding+warning. Bug
       16676[9].

     • Decoding of PFCP IE 'PFD Contents' results in "malformed packet".
       Bug 16704[10].

     • RFH2 Header with 32 or less bytes of NameValue will not parse out
       that info. Bug 16733[11].

     • CDP: Port ID TLV followed by Type 1009 TLV triggers [Malformed
       Packet]. Bug 16742[12].

     • tshark crashed when processing opcda. Bug 16746[13].

     • tshark with --export-dicom gives “Segmentation fault (core
       dumped)”. Bug 16748[14].

  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

   ASTERIX, BSSAP, CDP, CoAP, DCERPC SPOOLSS, DCOM, DICOM, DVB-S2,
   E.212, GBCS, GSM RR, GSM SMS, IEEE 802.11, Kafka, MQ, Nano, NAS 5GS,
   NIS+, NR RRC, PacketLogger, PFCP, RTPS, systemd Journal, TDS, TN3270,
   and TN5250

  New and Updated Capture File Support

   PacketLogger and pcapng

 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[15] 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[16] 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[17].

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

 Frequently Asked Questions

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

  Last updated 2020-08-12 17:53:44 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2020-10
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16672
   3. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-17498
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16623
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16662
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16664
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16668
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16670
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16676
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16704
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16733
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16742
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16746
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16748
  15. https://www.wireshark.org/download.html#thirdparty
  16. https://ask.wireshark.org/
  17. https://www.wireshark.org/lists/
  18. https://bugs.wireshark.org/
  19. https://www.wireshark.org/faq.html


Digests

wireshark-3.2.6.tar.xz: 31635628 bytes
SHA256(wireshark-3.2.6.tar.xz)=ebb1eebe39bcecee02195dc328dd25f6862fc9e9dea4c2e29eae50537d5eb4f2
RIPEMD160(wireshark-3.2.6.tar.xz)=09dcd3a088aa339e18871b053c9c8d8414b25a6a
SHA1(wireshark-3.2.6.tar.xz)=e8f3e6cb9072670c8bdbbff7e5fe3ccd5203d35e

Wireshark-win64-3.2.6.exe: 60127072 bytes
SHA256(Wireshark-win64-3.2.6.exe)=9c211a6eda5f69b2c10dd1a794f8a438c1dafbe5da4879b807be496d8f29a6c4
RIPEMD160(Wireshark-win64-3.2.6.exe)=b7b61d4529ba496f51f3ac024d1e600d6067b5ca
SHA1(Wireshark-win64-3.2.6.exe)=f511c383cd0fcd946e1e45ad302c0c6980631f60

Wireshark-win32-3.2.6.exe: 54946856 bytes
SHA256(Wireshark-win32-3.2.6.exe)=1b0b2a495878710417bb49640971d8188039c60d669a5ca8cfa273b027274d49
RIPEMD160(Wireshark-win32-3.2.6.exe)=15b647b21f634f0915ada7967ec07283a8ff940b
SHA1(Wireshark-win32-3.2.6.exe)=4d0f9ae18a4f3f48b4d291b8e29e59128745fcb7

Wireshark-win32-3.2.6.msi: 43106304 bytes
SHA256(Wireshark-win32-3.2.6.msi)=9af91fe9a26c5c5d8beecec5cdcb7020e2af44ab8c59cc8743dc6e20d16a0c37
RIPEMD160(Wireshark-win32-3.2.6.msi)=7e1201a6d3163c5d1dcda7068a8f15ead4065cd6
SHA1(Wireshark-win32-3.2.6.msi)=ca7edd76834e153a8e1465e6ebc58b011000b188

Wireshark-win64-3.2.6.msi: 48390144 bytes
SHA256(Wireshark-win64-3.2.6.msi)=d9682bff0a00d4a9cd58ea80540da81013a0700d44e506729893d4baef32ed5b
RIPEMD160(Wireshark-win64-3.2.6.msi)=4fc039e4bd8a386e57f4e0284e548fd1f2a08798
SHA1(Wireshark-win64-3.2.6.msi)=ecc95fdeb9a9f73d8ff248d43818dc4ef81f57e7

WiresharkPortable_3.2.6.paf.exe: 36687280 bytes
SHA256(WiresharkPortable_3.2.6.paf.exe)=886e45f3b3b3a25b1bbb7c65a4a5cd4c22e6635a73e5d8196d08f23f86911a2f
RIPEMD160(WiresharkPortable_3.2.6.paf.exe)=300a71ab95d97287f5723b32b8aa58b0fb7145e1
SHA1(WiresharkPortable_3.2.6.paf.exe)=eb380345293092fbe11c8c936d9ff8afb58ea7ab

Wireshark 3.2.6 Intel 64.dmg: 97726755 bytes
SHA256(Wireshark 3.2.6 Intel 64.dmg)=e63b7345e8a068a4c3e6dcd8b2de61fe66c03e78f3c8002a94829d152e1566d5
RIPEMD160(Wireshark 3.2.6 Intel 64.dmg)=bb638976af3258e556dbc9315e972ef26b09a673
SHA1(Wireshark 3.2.6 Intel 64.dmg)=31827acde32986cb2722228a49179a1c733f5c01

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