Wireshark-announce: [Wireshark-announce] Wireshark 3.0.10 is now available
From: Wireshark announcements <[email protected]>
Date: Wed, 8 Apr 2020 18:18:16 -0700
I'm proud to announce the release of Wireshark 3.0.10.


 What is Wireshark?

 What’s New

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2020-07[1] The BACapp dissector could crash. Bug
       16474[2]. CVE-2020-11647[3].

   The following bugs have been fixed:

     • RTCP Bye without optional reason reported as [Malformed Packet].
       Bug 16434[4].

     • [oss-fuzz] #20732: Undefined-shift in dissect_rtcp. Bug 16445[5].

     • tshark logs: "…​could not be opened: Too many open files.". Bug
       16457[6].

     • Typo in About Wireshark > Keyboard Shortcuts > Unignore All
       Displayed. Bug 16472[7].

     • [oss-fuzz] #21541: Stack-overflow in fAbstractSyntaxNType. Bug
       16474[8].

     • tshark live capture finishes with a use-after-free. Bug 16487[9].

  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

   AFS, BACapp, Bluetooth, Diameter3GPP, Modbus/TCP, NAS 5GS, pcap, and
   RTCP

  New and Updated Capture File Support

   pcap

  New and Updated Capture Interfaces 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[10] 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[11] 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[12].

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

 Frequently Asked Questions

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

  Last updated 2020-04-08 22:32:19 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2020-07
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16474
   3. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11647
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16434
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16445
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16457
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16472
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16474
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16487
  10. https://www.wireshark.org/download.html#thirdparty
  11. https://ask.wireshark.org/
  12. https://www.wireshark.org/lists/
  13. https://bugs.wireshark.org/
  14. https://www.wireshark.org/faq.html


Digests

wireshark-3.0.10.tar.xz: 30876288 bytes
SHA256(wireshark-3.0.10.tar.xz)=7877d78d200ef0329533c15a3c7bae1a26ef284aa831a5403059766d184662ea
RIPEMD160(wireshark-3.0.10.tar.xz)=b653fb8a172399610e49142ced9b46df49399463
SHA1(wireshark-3.0.10.tar.xz)=a62470f3b9adc755a6ff08d596d59a7447d1a04d

Wireshark-win32-3.0.10.exe: 54040296 bytes
SHA256(Wireshark-win32-3.0.10.exe)=3a1673c4c5e5a32bd291adeb4d5b39529bf1a0cdb6620b82d095a7bf4f074567
RIPEMD160(Wireshark-win32-3.0.10.exe)=8a18dd467c7001b5d02e3616ed23db3f05cb3679
SHA1(Wireshark-win32-3.0.10.exe)=a4937e6892a65142273e99fc2ee9e093f1c2d960

Wireshark-win64-3.0.10.exe: 59247232 bytes
SHA256(Wireshark-win64-3.0.10.exe)=6b4b03e98fda90684f5405fcc7da18a23e4d94e1720a4c4d3035821ce6c8df11
RIPEMD160(Wireshark-win64-3.0.10.exe)=4821b5f742982de1b77587974b067289bdae920f
SHA1(Wireshark-win64-3.0.10.exe)=8173928fea9e55c1018006fb1196ddbd4d607100

Wireshark-win64-3.0.10.msi: 47210496 bytes
SHA256(Wireshark-win64-3.0.10.msi)=3e5fa9942b2b044a399fb8fc3b9a77c44ad71f95f02bf55cf853c67e14689e0b
RIPEMD160(Wireshark-win64-3.0.10.msi)=98ef81cb4c1f86c3eb458532ce81798e6d4fa864
SHA1(Wireshark-win64-3.0.10.msi)=5e8b3052e3edf70481110c643217d030f66bb281

Wireshark-win32-3.0.10.msi: 42033152 bytes
SHA256(Wireshark-win32-3.0.10.msi)=9d7850fbbaf49f47675fc2237da1433bf28c8c0c1bd9fffd25a29372912f7fc0
RIPEMD160(Wireshark-win32-3.0.10.msi)=1bd9e377f51ee4c4ab6cb3e505a75a877fbb4a81
SHA1(Wireshark-win32-3.0.10.msi)=a6fc4a8604cdc0bf9f6a251fe0d5bd1ca3a4e0b8

WiresharkPortable_3.0.10.paf.exe: 35801368 bytes
SHA256(WiresharkPortable_3.0.10.paf.exe)=a3da277e061704b0db7c2d06fa72e3c1870dfef31d839522255d0dc57a7cef08
RIPEMD160(WiresharkPortable_3.0.10.paf.exe)=4527cabc56d26c39b2e1089f188f9ad9ef258696
SHA1(WiresharkPortable_3.0.10.paf.exe)=6b9850b8d2fbf37ac8393f4ebd09b92e5e0716de

Wireshark 3.0.10 Intel 64.dmg: 93079016 bytes
SHA256(Wireshark 3.0.10 Intel 64.dmg)=c82ca0e8baee1d530140e8ef8749a0930ecb87944b9e12c6fb591dbaab688e5c
RIPEMD160(Wireshark 3.0.10 Intel 64.dmg)=41f8a3506ed1b22de8919acd01d096994256dcf6
SHA1(Wireshark 3.0.10 Intel 64.dmg)=b9783b18aa7add2d8d47d40fd8115d443de0dbc8

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