[Gerald Combs <gerald@xxxxxxxxxxxxx>]

I'm proud to announce the release of Wireshark 2.4.12.

     __________________________________________________________________

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:
     * [1]wnpa-sec-2019-02 The P_MUL dissector could crash. [2]Bug 15337.
       [3]CVE-2019-5717.
     * [4]wnpa-sec-2019-03 The RTSE dissector and other dissectors could
       crash. [5]Bug 15373. [6]CVE-2019-5718.
     * [7]wnpa-sec-2019-04 The ISAKMP dissector could crash. [8]Bug 15374.
       [9]CVE-2019-5719.
     * [10]wnpa-sec-2019-05 The ISAKMP dissector could crash. [11]Bug
       14470.

   The following bugs have been fixed:
     * console.lua not found in a folder with non-ASCII characters in its
       name. [12]Bug 15118.
     * Disabling Update list of packets in real time. will generally
       trigger crash after three start capture, stop capture cycles.
       [13]Bug 15263.
     * UDP Multicast Stream double counts. [14]Bug 15271.
     * text2pcap et al. set snaplength to 64kiB-1, while processing frames
       of 256kiB. [15]Bug 15292.
     * Builds without libpcap fail if the libpcap headers aren't
       installed. [16]Bug 15317.
     * TCAP AnalogRedirectRecord parameter incorrectly coded as mandatory
       in QualReq_rr message. [17]Bug 15350.
     * Wireshark jumps behind other windows when opening UAT dialogs.
       [18]Bug 15366.
     * Pathnames containing non-ASCII characters are mangled in error
       dialogs on Windows. [19]Bug 15367.
     * Executing -z http,stat -r file.pcapng throws a segmentation fault.
       [20]Bug 15369.
     * IS-41 TCAP RegistrationNotification Invoke has borderCellAccess
       parameter coded as tag 50 (as denyAccess) but should be 58. [21]Bug
       15372.
     * GTPv2 APN dissect problem. [22]Bug 15383.

  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

   ANSI MAP, ENIP, GSM A, GTPv2, IMF, ISAKMP, P_MUL, RTSE, and TCAP

  New and Updated Capture File Support

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

  New and Updated Capture Interfaces support

   There are no new or updated capture interfaces supported in this
   release.
     __________________________________________________________________

Getting Wireshark

   Wireshark source code and installation packages are available from
   [23]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 [24]download page 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.
     __________________________________________________________________

Known Problems

   Dumpcap might not quit if Wireshark or TShark crashes. ([25]Bug 1419)

   The BER dissector might infinitely loop. ([26]Bug 1516)

   Capture filters aren't applied when capturing from named pipes.
   ([27]Bug 1814)

   Filtering tshark captures with read filters (-R) no longer works.
   ([28]Bug 2234)

   Application crash when changing real-time option. ([29]Bug 4035)

   Wireshark and TShark will display incorrect delta times in some cases.
   ([30]Bug 4985)

   Wireshark should let you work with multiple capture files. ([31]Bug
   10488)
     __________________________________________________________________

Getting Help

   Community support is available on [32]Wireshark's Q&A site and on the
   wireshark-users mailing list. Subscription information and archives for
   all of Wireshark's mailing lists can be found on [33]the web site.

   Official Wireshark training and certification are available from
   [34]Wireshark University.
     __________________________________________________________________

Frequently Asked Questions

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

   Last updated 2019-01-08 18:12:46 UTC

References

   1. https://www.wireshark.org/security/wnpa-sec-2019-02.html
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15337
   3. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5717
   4. https://www.wireshark.org/security/wnpa-sec-2019-03.html
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15373
   6. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5718
   7. https://www.wireshark.org/security/wnpa-sec-2019-04.html
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15374
   9. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5719
  10. https://www.wireshark.org/security/wnpa-sec-2019-05.html
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14470
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15118
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15263
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15271
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15292
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15317
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15350
  18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15366
  19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15367
  20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15369
  21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15372
  22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15383
  23. https://www.wireshark.org/download.html
  24. https://www.wireshark.org/download.html#thirdparty
  25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
  26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
  27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
  28. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  31. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  32. https://ask.wireshark.org/
  33. https://www.wireshark.org/lists/
  34. http://www.wiresharktraining.com/
  35. https://www.wireshark.org/faq.html


Digests

wireshark-2.4.12.tar.xz: 29135844 bytes
SHA256(wireshark-2.4.12.tar.xz)=1c1b05569b6dad161b8f1eb1e33d8e497c774622fcf5c8f2d487011d3238aaf1
RIPEMD160(wireshark-2.4.12.tar.xz)=4e3fdc5711bfde4e1dfd1d830a3ca58fe2cb9972
SHA1(wireshark-2.4.12.tar.xz)=eae82e56d0e449531c81680da6cd1f9c481a6844

Wireshark-win64-2.4.12.exe: 58000928 bytes
SHA256(Wireshark-win64-2.4.12.exe)=b8cab1f10f31beb1a29794713f9383d0f0be10720306cfcf11a1478297f5c096
RIPEMD160(Wireshark-win64-2.4.12.exe)=6f8febea0d15206f9725b3351c6ea95ecccdc789
SHA1(Wireshark-win64-2.4.12.exe)=7dc058842c9d6805b757f1f8b57fdfa1dab9d09a

Wireshark-win32-2.4.12.exe: 52798176 bytes
SHA256(Wireshark-win32-2.4.12.exe)=262d7c8190502c6c0648f638ed6e0e910a7798846f18c53e76aaa331bd4f8d08
RIPEMD160(Wireshark-win32-2.4.12.exe)=c2adf8a34bdd279a0defbea2e40a8485a2ce15e2
SHA1(Wireshark-win32-2.4.12.exe)=287e4d77388585f850f3aac9f90eb72325c36fb7

Wireshark-win64-2.4.12.msi: 47095808 bytes
SHA256(Wireshark-win64-2.4.12.msi)=bfd0dfcdbe0f9486445ff650d869c08d55ac7617ab4c6c360e811f3ba84f7230
RIPEMD160(Wireshark-win64-2.4.12.msi)=76bdf1f99dc0aca2469f824765bb10cd7ae30832
SHA1(Wireshark-win64-2.4.12.msi)=82bda355d2d531c678765419cfbee32ad8cf5334

Wireshark-win32-2.4.12.msi: 42037248 bytes
SHA256(Wireshark-win32-2.4.12.msi)=1fdc120d15dc63fc107c75a4de5f1991102db95dfd0fd446a4b3d3ba00c565eb
RIPEMD160(Wireshark-win32-2.4.12.msi)=e3ccb9186b0a0fc3edd541e49d3801fdfb0a50c4
SHA1(Wireshark-win32-2.4.12.msi)=a2830d77c3805959380eef142b467961d2597d88

WiresharkPortable_2.4.12.paf.exe: 45453168 bytes
SHA256(WiresharkPortable_2.4.12.paf.exe)=1971739068280b86a5b9b68bc713cc0eadbdb42dbd618621ee3a2973597d1b1c
RIPEMD160(WiresharkPortable_2.4.12.paf.exe)=3ed323429f55e6cb72f7fda289cea1c5d5364abd
SHA1(WiresharkPortable_2.4.12.paf.exe)=5d16c7e4b02c2f96a233f5272ecacd4eec131954

Wireshark 2.4.12 Intel 64.dmg: 42582955 bytes
SHA256(Wireshark 2.4.12 Intel
64.dmg)=b31c2f90316f1fc9f806406a9c7f4cc4ea2c9fa6b697d402eaf884a973fc4325
RIPEMD160(Wireshark 2.4.12 Intel
64.dmg)=766d2d1067d647ceb4103d2f64ed3d9c8381e2d4
SHA1(Wireshark 2.4.12 Intel 64.dmg)=8d352dddaa99cb241f45071fd41c71b14d2bee20

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