Wireshark-announce: [Wireshark-announce] Wireshark 2.4.10 is now available
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Thu, 11 Oct 2018 15:52:33 -0700
I'm proud to announce the release of Wireshark 2.4.10. __________________________________________________________________ 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-47 MS-WSP dissector crash. [2]Bug 15119. [3]CVE-2018-18227. * [4]wnpa-sec-2018-50 OpcUA dissector crash. [5]CVE-2018-12086. The following bugs have been fixed: * HTTP2 dissector decodes first SSL record only. [6]Bug 11173. * Undocumented sub-option for -N option in man page and tshark -N help. [7]Bug 14826. * Mishandling of Port Control Protocol option padding. [8]Bug 14950. * MGCP: parameter lines are case-insensitive. [9]Bug 15008. * details of 2nd sub-VSA in bundled RADIUS VSA are incorrect. [10]Bug 15073. * Heuristic DPLAY dissector fails to recognize DPLAY packets. [11]Bug 15092. * gsm_rlcmac_dl dissector exception. [12]Bug 15112. * Buildbot crash output: fuzz-2018-09-07-29306.pcap. [13]Bug 15119. * Wildcard expansion doesn't work on Windows 10 for command-line programs in cmd.exe or PowerShell. [14]Bug 15151. * SSL Reassembly Error New fragment past old data limits. [15]Bug 15158. 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 ASN.1 PER, CIP, DPLAY, HTTP, MGCP, MS-WSP, OpcUa, PCP, RADIUS, and TLS New and Updated Capture File Support Ascend, and pcapng 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 [16]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 [17]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. ([18]Bug 1419) The BER dissector might infinitely loop. ([19]Bug 1516) Capture filters aren't applied when capturing from named pipes. ([20]Bug 1814) Filtering tshark captures with read filters (-R) no longer works. ([21]Bug 2234) Application crash when changing real-time option. ([22]Bug 4035) Wireshark and TShark will display incorrect delta times in some cases. ([23]Bug 4985) Wireshark should let you work with multiple capture files. ([24]Bug 10488) __________________________________________________________________ Getting Help Community support is available on [25]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 [26]the web site. Official Wireshark training and certification are available from [27]Wireshark University. __________________________________________________________________ Frequently Asked Questions A complete FAQ is available on the [28]Wireshark web site. __________________________________________________________________ Last updated 2018-10-11 20:54:40 UTC References 1. https://www.wireshark.org/security/wnpa-sec-2018-47.html 2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15119 3. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-18227 4. https://www.wireshark.org/security/wnpa-sec-2018-50.html 5. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12086 6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11173 7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14826 8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14950 9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15008 10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15073 11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15092 12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15112 13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15119 14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15151 15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15158 16. https://www.wireshark.org/download.html 17. https://www.wireshark.org/download.html#thirdparty 18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419 19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516 20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814 21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234 22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035 23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985 24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488 25. https://ask.wireshark.org/ 26. https://www.wireshark.org/lists/ 27. http://www.wiresharktraining.com/ 28. https://www.wireshark.org/faq.html Digests wireshark-2.4.10.tar.xz: 29111700 bytes SHA256(wireshark-2.4.10.tar.xz)=d111d534baab687cf9d22d9aedbeb279214d58f9f38c496780697b626072882b RIPEMD160(wireshark-2.4.10.tar.xz)=06e7536a480701086ab89946ac78e516a8bde3cb SHA1(wireshark-2.4.10.tar.xz)=654032a123ccb9587f788d50d7fb5d90d9ba0e91 Wireshark-win64-2.4.10.exe: 57982160 bytes SHA256(Wireshark-win64-2.4.10.exe)=5560ba9038ac5c068ce7e4903381c45c7dff83a367af37cc389de88eb5a96527 RIPEMD160(Wireshark-win64-2.4.10.exe)=ad1af79e4ce863fc0ca334ab238c30ae48856a21 SHA1(Wireshark-win64-2.4.10.exe)=aa878b82acccd3422ba2cdf7d882d248e52b3a79 Wireshark-win32-2.4.10.exe: 52783184 bytes SHA256(Wireshark-win32-2.4.10.exe)=e82693cc7e969196f62e07cd397e472b4977a607bdccbcb20366796da6b8b4d7 RIPEMD160(Wireshark-win32-2.4.10.exe)=599a2792ba4e72425176de2b11000f083fb56b10 SHA1(Wireshark-win32-2.4.10.exe)=527ea51bcc31c7886b89df1be99f472b561df0e1 Wireshark-win32-2.4.10.msi: 42024960 bytes SHA256(Wireshark-win32-2.4.10.msi)=4063ce299184a12a07126a83f835309b5bd41f563d211a8aaf5432cc33ad8e60 RIPEMD160(Wireshark-win32-2.4.10.msi)=22ea3cb77aab4ba580979fa6227c480baa689aea SHA1(Wireshark-win32-2.4.10.msi)=c645d871e3fbad3f17b03a4bde2ec62c1745f394 Wireshark-win64-2.4.10.msi: 47063040 bytes SHA256(Wireshark-win64-2.4.10.msi)=f6ce5b2fa1f4c0ed32bf2c95a21b77f626e4da9af7b137b7fd60d475aba6c687 RIPEMD160(Wireshark-win64-2.4.10.msi)=a20edab6b01d7d8267746522630fa3f9e97319cc SHA1(Wireshark-win64-2.4.10.msi)=56bf78b12e7f459ffb3844c1beedb4713ee11132 WiresharkPortable_2.4.10.paf.exe: 45436640 bytes SHA256(WiresharkPortable_2.4.10.paf.exe)=41630b20f0a884bac5c195ddf2e66c10e63484818395a329d82186b4fa521ebf RIPEMD160(WiresharkPortable_2.4.10.paf.exe)=75bd14e0808c946ebfae2f48ecef7756d3fa6f5f SHA1(WiresharkPortable_2.4.10.paf.exe)=ea5aa4d8b941d1ac31dfa44bdab35603bbbb66ed Wireshark 2.4.10 Intel 64.dmg: 42540737 bytes SHA256(Wireshark 2.4.10 Intel 64.dmg)=eb537a03340a46178594664fd5058e4cd3702060fbb98a8dd61dd41dc60ea96b RIPEMD160(Wireshark 2.4.10 Intel 64.dmg)=8d71185ae01b68daacc29e5f2fbbc410cf85cba8 SHA1(Wireshark 2.4.10 Intel 64.dmg)=595be1ad5a414959ba3df8d1600976c5efe8896e 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
- Prev by Date: [Wireshark-announce] Wireshark 2.6.4 is now available
- Previous by thread: [Wireshark-announce] Wireshark 2.6.4 is now available
- Index(es):