Wireshark-dev: [Wireshark-dev] Wireshark 4.0.3 is now available

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 18 Jan 2023 13:58:42 -0800
I'm proud to announce the release of Wireshark 4.0.3.


 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

  We do not ship official 32-bit Windows packages for Wireshark 4.0 and
  later. If you need to use Wireshark on that platform, we recommend
  using the latest 3.6 release. Issue 17779[1]

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2023-01[2] EAP dissector crash. Issue 18622[3].

     • wnpa-sec-2023-02[4] NFS dissector memory leak. Issue 18628[5].

     • wnpa-sec-2023-03[6] Dissection engine crash. Issue 18766[7].

     • wnpa-sec-2023-04[8] GNW dissector crash. Issue 18779[9].

     • wnpa-sec-2023-05[10] iSCSI dissector crash. Issue 18796[11].

     • wnpa-sec-2023-06[12] Multiple dissector excessive loops. Issue
       18711[13]. Issue 18720[14], Issue 18737[15].

     • wnpa-sec-2023-07[16] TIPC dissector crash. Issue 18770[17].

   The following bugs have been fixed:

     • Qt: After modifying coloring rules, the coloring rule applied to
       the first packet reflects the coloring rules previously in
       effect. Issue 12475[18].

     • Help file doesn’t display for extcap interfaces. Issue 15592[19].

     • For USB traffic on XHC20 interface destination is always given as
       Host. Issue 16768[20].

     • Wireshark Expert Info - cannot deselect the limit to display
       filter tick box. Issue 18461[21].

     • Wrong pointer conversion in get_data_source_tvb_by_name() Issue
       18517[22].

     • Wrong number of bits skipped while decoding an empty UTF8String
       on UPER packet. Issue 18702[23].

     • Crash when analyzing protobuf packets. Issue 18730[24].

     • Uninitialized values in various dissectors. Issue 18742[25].

     • String (GeoIP country/city) ordering doesn’t work in Endpoints.
       Issue 18749[26].

     • Wireshark crashes with an assertion failure on stray minus in
       filter. Issue 18750[27].

     • IO Graph: Add new graph only works until the 10th graph. Issue
       18762[28].

     • Fuzz job crash output: fuzz-2022-12-30-11007.pcap. Issue
       18770[29].

     • Q.850 - error in label for cause 0x7F. Issue 18780[30].

     • Uninitialized values in CoAP and RTPS dissectors. Issue
       18785[31].

     • Screenshots in AppStream metainfo.xml file not available. Issue
       18801[32].

  New and Updated Features

  Removed Features and Support

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   ASTERIX, BEEP, BGP, BPv6, CoAP, EAP, GNW, GSM A-bis P-GSL, iSCSI,
   ISUP, LwM2M-TLV, MBIM, NBAP, NFS, OBD-II, OPUS, ProtoBuf, RLC, ROHC,
   RTPS, Telnet, TIPC, and USB

  New and Updated Capture File Support

   There is no new or updated capture file support in this release.

  New File Format Decoding Support

   There is no new or updated file format 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[33] 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 "Help › About
  Wireshark › Folders" or `tshark -G 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[34] 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[35].

  Bugs and feature requests can be reported on the issue tracker[36].

  You can learn protocol analysis and meet Wireshark’s developers at
  SharkFest[37].

 How You Can Help

  The Wireshark Foundation helps as many people as possible understand
  their networks as much as possible. You can find out more and donate
  at wiresharkfoundation.org[38].

 Frequently Asked Questions

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

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17779
   2. https://www.wireshark.org/security/wnpa-sec-2023-01
   3. https://gitlab.com/wireshark/wireshark/-/issues/18622
   4. https://www.wireshark.org/security/wnpa-sec-2023-02
   5. https://gitlab.com/wireshark/wireshark/-/issues/18628
   6. https://www.wireshark.org/security/wnpa-sec-2023-03
   7. https://gitlab.com/wireshark/wireshark/-/issues/18766
   8. https://www.wireshark.org/security/wnpa-sec-2023-04
   9. https://gitlab.com/wireshark/wireshark/-/issues/18779
  10. https://www.wireshark.org/security/wnpa-sec-2023-05
  11. https://gitlab.com/wireshark/wireshark/-/issues/18796
  12. https://www.wireshark.org/security/wnpa-sec-2023-06
  13. https://gitlab.com/wireshark/wireshark/-/issues/18711
  14. https://gitlab.com/wireshark/wireshark/-/issues/18720
  15. https://gitlab.com/wireshark/wireshark/-/issues/18737
  16. https://www.wireshark.org/security/wnpa-sec-2023-07
  17. https://gitlab.com/wireshark/wireshark/-/issues/18770
  18. https://gitlab.com/wireshark/wireshark/-/issues/12475
  19. https://gitlab.com/wireshark/wireshark/-/issues/15592
  20. https://gitlab.com/wireshark/wireshark/-/issues/16768
  21. https://gitlab.com/wireshark/wireshark/-/issues/18461
  22. https://gitlab.com/wireshark/wireshark/-/issues/18517
  23. https://gitlab.com/wireshark/wireshark/-/issues/18702
  24. https://gitlab.com/wireshark/wireshark/-/issues/18730
  25. https://gitlab.com/wireshark/wireshark/-/issues/18742
  26. https://gitlab.com/wireshark/wireshark/-/issues/18749
  27. https://gitlab.com/wireshark/wireshark/-/issues/18750
  28. https://gitlab.com/wireshark/wireshark/-/issues/18762
  29. https://gitlab.com/wireshark/wireshark/-/issues/18770
  30. https://gitlab.com/wireshark/wireshark/-/issues/18780
  31. https://gitlab.com/wireshark/wireshark/-/issues/18785
  32. https://gitlab.com/wireshark/wireshark/-/issues/18801
  33. https://www.wireshark.org/download.html
  34. https://ask.wireshark.org/
  35. https://www.wireshark.org/lists/
  36. https://gitlab.com/wireshark/wireshark/-/issues
  37. https://sharkfest.wireshark.org
  38. https://wiresharkfoundation.org
  39. https://www.wireshark.org/faq.html


Digests

wireshark-4.0.3.tar.xz: 41383164 bytes
SHA256(wireshark-4.0.3.tar.xz)=6c51e15bcc0afb93734e686dbff354ffd159f570bd2904bcbbad6f3feb7e9511
SHA1(wireshark-4.0.3.tar.xz)=243b0057cfe6d447662e81b5646110aaf8b63c81

Wireshark-win64-4.0.3.exe: 78728232 bytes
SHA256(Wireshark-win64-4.0.3.exe)=26feddeb71571e63851c10c16325bd1d19e0175088c0e2732ef25f586b560fe7
SHA1(Wireshark-win64-4.0.3.exe)=bfaa980b73c8690eb019b2d84fb83dd16bb1c01c

Wireshark-win64-4.0.3.msi: 52125696 bytes
SHA256(Wireshark-win64-4.0.3.msi)=03224720bb78344db75d3d73dd3e0379bba18fbd7578e912743f72733a839a16
SHA1(Wireshark-win64-4.0.3.msi)=06ce523d1df785ff02b96cc6954bfc4b00b82d0a

WiresharkPortable64_4.0.3.paf.exe: 45482296 bytes
SHA256(WiresharkPortable64_4.0.3.paf.exe)=590a04368fbea44b627eb276da6c4cb2bc1737f5b37b6564553091dd4b6c40f8
SHA1(WiresharkPortable64_4.0.3.paf.exe)=05da24c7082c78316a87863b4d69ca42ef0c6447

Wireshark 4.0.3 Arm 64.dmg: 62713393 bytes
SHA256(Wireshark 4.0.3 Arm 64.dmg)=6f942be07fbbdaf53118e457ccb0392b00c2b5854167d77884a7b3492eb8b6a6
SHA1(Wireshark 4.0.3 Arm 64.dmg)=451959dcf2663c6289664ef5b88aa2f707527f94

Wireshark 4.0.3 Intel 64.dmg: 65623912 bytes
SHA256(Wireshark 4.0.3 Intel 64.dmg)=aca5a032af016e5bf61f2b64dfc3c64cb3c51276768ca5fc8cb5f5cd264b559a
SHA1(Wireshark 4.0.3 Intel 64.dmg)=eb1895317ff5deba3b3af3a240af1d81049060eb

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