Wireshark-announce: [Wireshark-announce] Wireshark 2.2.12 is now available
Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Thu, 11 Jan 2018 12:05:14 -0800
I'm proud to announce the release of Wireshark 2.2.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-2018-01
       Multiple dissectors could crash. ([2]Bug 14253) [3]CVE-2018-5336
     * [4]wnpa-sec-2018-02
       The MRDISC dissector could crash. ([5]Bug 14299, [6]Bug 13707)
       [7]CVE-2017-17997
     * [8]wnpa-sec-2018-03
       The IxVeriWave file parser could crash. ([9]Bug 14297)
       [10]CVE-2018-5334
     * [11]wnpa-sec-2018-04
       The WCP dissector could crash. ([12]Bug 14251) [13]CVE-2018-5335

   Prior to this release dumpcap enabled the Linux kernel's BPF JIT
   compiler via the net.core.bpf_jit_enable sysctl. This could make
   systems more vulnerable to Spectre variant 1 ([14]CVE-2017-5753) and
   this feature has been removed ([15]Bug 14313).

   The following bugs have been fixed:
     * First start with non-empty extcap folder after install or reboot
       hangs at "initializing tap listeners". ([16]Bug 12845)
     * SIP Statistics extract does not work. ([17]Bug 13942)
     * Service Response Time - SCSI dialog crashes. ([18]Bug 14144)
     * SOCKS pseudo header displays incorrect Version value. ([19]Bug
       14262)
     * Only first variable of list is dissected in NTP Control request
       message. ([20]Bug 14268)
     * NTP Authenticator field dissection fails if padding is used.
       ([21]Bug 14269)
     * There is a potential buffer underflow in File_read_line function in
       epan/wslua/wslua_file.c file. ([22]Bug 14295)
     * Saving a temporary capture file may not result in the temporary
       file being removed. ([23]Bug 14298)

  New and Updated Features

   There are no new features in this release.

  New File Format Decoding Support

   There are no new file formats in this release.

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   MRDISC, NTP, SCTP, SOCKS, and WCP

  New and Updated Capture File Support

   Ixia IxVeriWave

  New and Updated Capture Interfaces support

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

  Major API Changes

   There are no major API changes in this release.
     __________________________________________________________________

Getting Wireshark

   Wireshark source code and installation packages are available from
   [24]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 [25]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. ([26]Bug 1419)

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

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

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

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

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

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

Getting Help

   Community support is available on [33]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 [34]the web site.

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

Frequently Asked Questions

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

   Last updated 2018-01-11 17:57:46 UTC

References

   1. https://www.wireshark.org/security/wnpa-sec-2018-01.html
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14253
   3. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5336
   4. https://www.wireshark.org/security/wnpa-sec-2018-02.html
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14299
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13707
   7. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17997
   8. https://www.wireshark.org/security/wnpa-sec-2018-03.html
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14297
  10. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5334
  11. https://www.wireshark.org/security/wnpa-sec-2018-04.html
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14251
  13. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5335
  14. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5753
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14313
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13942
  18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14144
  19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14262
  20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14268
  21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14269
  22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14295
  23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14298
  24. https://www.wireshark.org/download.html
  25. https://www.wireshark.org/download.html#thirdparty
  26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
  27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
  28. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
  29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  31. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  32. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  33. https://ask.wireshark.org/
  34. https://www.wireshark.org/lists/
  35. http://www.wiresharktraining.com/
  36. https://www.wireshark.org/faq.html


Digests

wireshark-2.2.12.tar.bz2: 32387381 bytes
SHA256(wireshark-2.2.12.tar.bz2)=3274458d1bb1658a5001465ecb07c7cbfc709571ef36bd062897570d4bab3ebc
RIPEMD160(wireshark-2.2.12.tar.bz2)=782cf5218d79af35087ca2f8087bc54ffeede65c
SHA1(wireshark-2.2.12.tar.bz2)=a52419a1b0b922448f56a271d0f8d725d2e62caf

Wireshark-win32-2.2.12.exe: 44651848 bytes
SHA256(Wireshark-win32-2.2.12.exe)=42b520e2b5003963e399f97eb23ad74a49ad0562b94558db32d2ceb07e0c0fae
RIPEMD160(Wireshark-win32-2.2.12.exe)=7d0ff3681107d42521f1a53d675f41f939cefdd5
SHA1(Wireshark-win32-2.2.12.exe)=6da2e58d8a2d86af9f0caff736afe5dee4805fcd

Wireshark-win64-2.2.12.exe: 56155344 bytes
SHA256(Wireshark-win64-2.2.12.exe)=95ef0011ab04ed2a52eb5f4c26d4ccede262c4441b80337a494c8e97f7b117b7
RIPEMD160(Wireshark-win64-2.2.12.exe)=b47a00664354941edfce7a3d95a0f22c3d5195ec
SHA1(Wireshark-win64-2.2.12.exe)=9f5a3bf2ad8e6f5abb6578c625a04f3570ffc815

WiresharkPortable_2.2.12.paf.exe: 46291296 bytes
SHA256(WiresharkPortable_2.2.12.paf.exe)=b729074a6e93eed3e80c117e3a950a805d7df6e24afbac13d0275ad1969233b1
RIPEMD160(WiresharkPortable_2.2.12.paf.exe)=207a94534b4d55a65b89592be9106ed2158acce6
SHA1(WiresharkPortable_2.2.12.paf.exe)=6331c88a6d2ae9cc0668572a5d778e5f791fe18f

Wireshark 2.2.12 Intel 64.dmg: 33526164 bytes
SHA256(Wireshark 2.2.12 Intel
64.dmg)=8a4bdc2d917df1c7f751c1ebbbdcfc1c074864f3e623fc4648016a65c4511e80
RIPEMD160(Wireshark 2.2.12 Intel
64.dmg)=6c631b55677ccc0b2f58c8577a91f7404290d308
SHA1(Wireshark 2.2.12 Intel 64.dmg)=572d72fa4ba524d471cbff8913d4ede8567c5f83

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