Wireshark-announce: [Wireshark-announce] Wireshark 3.2.9 is now available
From: Wireshark announcements <[email protected]>
Date: Wed, 9 Dec 2020 18:07:42 -0800
I'm proud to announce the release of Wireshark 3.2.9.


 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

     • wnpa-sec-2020-16[1] Kafka dissector memory leak. Bug 16739[2].
       CVE-2020-26418[3].

     • wnpa-sec-2020-17[4] USB HID dissector crash. Bug 16958[5].
       CVE-2020-26421[6].

     • wnpa-sec-2020-18[7] RTPS dissector memory leak. Bug 16994[8].
       CVE-2020-26420[9].

   The following bugs have been fixed:

     • SOME/IP: Wrong dissection of parameters after Array Bug
       16951[10].

     • Can editcap properly corrupt pcapng file with systemd journal
       export block? Bug 16965[11].

     • Crash when a GIOP ior.txt file is present Bug 16984[12].

     • Protobuf: failed to parse .proto file contains negative enum
       values or option values of number type Bug 16988[13].

     • MMRP dissector bug Bug 17005[14].

     • SSTP no longer recognized Bug 17024[15].

     • RFC2190 encapsulated H.263 bitfields masked wrong in Mode A Bug
       17025[16].

     • SOME/IP: Resetting offset of static_array Bug 17057[17].

     • SMB Dissector for TRANS2_QUERY_FS_INFO displays truncated FS Name
       & Label Bug 17064[18].

     • Wireshark does not display Arabic, Greek, some other characters
       correctly Bug 17070[19].

  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

   Ericsson HDLC, F5 Ethernet Trailer, GIOP, GSM A, HTTP, IEEE 802.11,
   Kafka, LLC, MMRP, NAS 5GS, NAS EPS, ProtoBuf, QUIC, Radiotap, RFC
   2190, RLC MAC, RTCP, RTPS, S1AP, SMB, SMB2, SOME/IP, and USB Video

  New and Updated Capture File Support

   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[20] 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[21] 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[22].

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

 Frequently Asked Questions

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

  Last updated 2020-12-09 22:15:04 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2020-16
   2. https://gitlab.com/wireshark/wireshark/-/issues/16739
   3. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26418
   4. https://www.wireshark.org/security/wnpa-sec-2020-17
   5. https://gitlab.com/wireshark/wireshark/-/issues/16958
   6. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26421
   7. https://www.wireshark.org/security/wnpa-sec-2020-18
   8. https://gitlab.com/wireshark/wireshark/-/issues/16994
   9. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26420
  10. https://gitlab.com/wireshark/wireshark/-/issues/16951
  11. https://gitlab.com/wireshark/wireshark/-/issues/16965
  12. https://gitlab.com/wireshark/wireshark/-/issues/16984
  13. https://gitlab.com/wireshark/wireshark/-/issues/16988
  14. https://gitlab.com/wireshark/wireshark/-/issues/17005
  15. https://gitlab.com/wireshark/wireshark/-/issues/17024
  16. https://gitlab.com/wireshark/wireshark/-/issues/17025
  17. https://gitlab.com/wireshark/wireshark/-/issues/17057
  18. https://gitlab.com/wireshark/wireshark/-/issues/17064
  19. https://gitlab.com/wireshark/wireshark/-/issues/17070
  20. https://www.wireshark.org/download.html#thirdparty
  21. https://ask.wireshark.org/
  22. https://www.wireshark.org/lists/
  23. https://gitlab.com/wireshark/wireshark/-/issues
  24. https://www.wireshark.org/faq.html


Digests

wireshark-3.2.9.tar.xz: 31671108 bytes
SHA256(wireshark-3.2.9.tar.xz)=ca5499aa1d292bcffaf302191188b27ae0ed2da1d7fa18534314c0b64cc03539
RIPEMD160(wireshark-3.2.9.tar.xz)=4d674acdf55fb0d319f4e7c11e1f57c91f231466
SHA1(wireshark-3.2.9.tar.xz)=aa1a0331c4921d7658a0ab29f6633f4aba6d9d95

Wireshark-win64-3.2.9.exe: 60087376 bytes
SHA256(Wireshark-win64-3.2.9.exe)=c14ac87fd5a4db2f82b653ba446d3d5e67213ffe31bc5493124578cc44b19262
RIPEMD160(Wireshark-win64-3.2.9.exe)=7454275108714a039ec718b5afa52ec63e41e866
SHA1(Wireshark-win64-3.2.9.exe)=93519c51dd63b123a648a3400e36afaf8e312405

Wireshark-win32-3.2.9.exe: 54934680 bytes
SHA256(Wireshark-win32-3.2.9.exe)=c7b05f6fc577aba5bc61f1779264205933487a11102f2467b88fc82d5668a8c3
RIPEMD160(Wireshark-win32-3.2.9.exe)=fb023c3ae76107a31c185fd1d2548c07c0f0a7d6
SHA1(Wireshark-win32-3.2.9.exe)=01b7591508d63a79e5731bdb16cef31eede38e4d

Wireshark-win32-3.2.9.msi: 43171840 bytes
SHA256(Wireshark-win32-3.2.9.msi)=cfe9e6a20cf72ab3db13d2b169240bb8ef702c0de525e701ebfd3655ca88fd96
RIPEMD160(Wireshark-win32-3.2.9.msi)=65d92e29aaee409f503c540137f40ff912a4133f
SHA1(Wireshark-win32-3.2.9.msi)=45ba3de64c7fd85ab970fe7d3429484176795340

Wireshark-win64-3.2.9.msi: 48427008 bytes
SHA256(Wireshark-win64-3.2.9.msi)=457d40187f32dd79c007338acb4da2833d245108fed33b17874a572576e8aebc
RIPEMD160(Wireshark-win64-3.2.9.msi)=6cdb440ab83137c7f7c605cd432acfb7116096c0
SHA1(Wireshark-win64-3.2.9.msi)=4001f2b44baec826607f222aa8720a3c149dceb2

WiresharkPortable_3.2.9.paf.exe: 36754104 bytes
SHA256(WiresharkPortable_3.2.9.paf.exe)=a578bbf822bfd19eb7fb2f10f4cb7a432a295d8a35d0c0b82384461497a56dfb
RIPEMD160(WiresharkPortable_3.2.9.paf.exe)=33953585b53ab9904ed1856a4f57040d919b3f81
SHA1(WiresharkPortable_3.2.9.paf.exe)=474eed848a9c779f6168c0955d0a43f7deeec236

Wireshark 3.2.9 Intel 64.dmg: 97503812 bytes
SHA256(Wireshark 3.2.9 Intel 64.dmg)=d2557ba99b22f3ee149c701a6fb9ac44ac5629c41e72c2ab4ed020a3ede2faca
RIPEMD160(Wireshark 3.2.9 Intel 64.dmg)=cb65ca8f64c64a48fb6f7bb00e429967de57b750
SHA1(Wireshark 3.2.9 Intel 64.dmg)=fb786a0677c73f8253bb31349379aaa61dc2c57c

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: OpenPGP_signature
Description: OpenPGP digital signature