Wireshark-users: [Wireshark-users] Wireshark 1.10.11 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 12 Nov 2014 12:33:43 -0800
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.10.11. __________________________________________________________ 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-2014-20 SigComp UDVM buffer overflow. ([2]Bug 10662) [3]CVE-2014-8710 * [4]wnpa-sec-2014-21 AMQP crash. ([5]Bug 10582) [6]CVE-2014-8711 * [7]wnpa-sec-2014-22 NCP crashes. ([8]Bug 10552, [9]Bug 10628) [10]CVE-2014-8712 [11]CVE-2014-8713 * [12]wnpa-sec-2014-23 TN5250 infinite loops. ([13]Bug 10596) [14]CVE-2014-8714 The following bugs have been fixed: * 6LoWPAN Mesh headers not treated as encapsulating address. ([15]Bug 10462) * UCP dissector bug of operation 31 - PID 0639 not recognized. ([16]Bug 10463) * iSCSI dissector rejects PDUs with "expected data transfer length" > 16M. ([17]Bug 10469) * GTPv2: trigging_tree under Trace information has wrong length. ([18]Bug 10470) * Attempt to render an SMS-DELIVER-REPORT instead of an SMS-DELIVER. ([19]Bug 10547) * IPv6 Mobility Option IPv6 Address/Prefix marks too many bytes for the address/prefix field. ([20]Bug 10576) * IPv6 Mobility Option Binding Authorization Data for FMIPv6 Authenticator field is read beyond the option data. ([21]Bug 10577) * IPv6 Mobility Option Mobile Node Link Layer Identifier Link-layer Identifier field is read beyond the option data. ([22]Bug 10578) * Malformed PTPoE announce packet. ([23]Bug 10611) * IPv6 Permanent Home Keygen Token mobility option includes too many bytes for the token field. ([24]Bug 10619) * IPv6 Redirect Mobility Option K and N bits are parsed incorrectly. ([25]Bug 10622) * IPv6 Care Of Test mobility option includes too many bytes for the Keygen Token field. ([26]Bug 10624) * IPv6 MESG-ID mobility option is parsed incorrectly. ([27]Bug 10625) * IPv6 AUTH mobility option parses Mobility SPI and Authentication Data incorrectly. ([28]Bug 10626) * IPv6 DNS-UPDATE-TYPE mobility option includes too many bytes for the MD identity field. ([29]Bug 10629) * IPv6 Local Mobility Anchor Address mobility option's code and reserved fields are parsed as 2 bytes instead of 1. ([30]Bug 10630) * TShark crashes when running with PDML on a specific packet. ([31]Bug 10651) * IPv6 Mobility Option Context Request reads an extra request. ([32]Bug 10676) 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 6LoWPAN, AMQP, GSM MAP, GTPv2, H.223, IEEE 802.11, iSCSI, MIH, Mobile IPv6, PTPoE, TN5250, and UCP New and Updated Capture File Support Catapult DCT2000, HP-UX nettl, pcap-ng, and Sniffer (DOS) __________________________________________________________ Getting Wireshark Wireshark source code and installation packages are available from [33]http://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 [34]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. ([35]Bug 1419) The BER dissector might infinitely loop. ([36]Bug 1516) Capture filters aren't applied when capturing from named pipes. ([37]Bug 1814) Filtering tshark captures with read filters (-R) no longer works. ([38]Bug 2234) The 64-bit Windows installer does not support Kerberos decryption. ([39]Win64 development page) Resolving ([40]Bug 9044) reopens ([41]Bug 3528) so that Wireshark no longer automatically decodes gzip data when following a TCP stream. Application crash when changing real-time option. ([42]Bug 4035) Hex pane display issue after startup. ([43]Bug 4056) Packet list rows are oversized. ([44]Bug 4357) Summary pane selected frame highlighting not maintained. ([45]Bug 4445) Wireshark and TShark will display incorrect delta times in some cases. ([46]Bug 4985) __________________________________________________________ Getting Help Community support is available on [47]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 [48]the web site. Official Wireshark training and certification are available from [49]Wireshark University. __________________________________________________________ Frequently Asked Questions A complete FAQ is available on the [50]Wireshark web site. __________________________________________________________ Last updated 2014-11-12 12:31:41 PST References 1. https://www.wireshark.org/security/wnpa-sec-2014-20.html 2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10662 3. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8710 4. https://www.wireshark.org/security/wnpa-sec-2014-21.html 5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10582 6. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8711 7. https://www.wireshark.org/security/wnpa-sec-2014-22.html 8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10552 9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10628 10. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8712 11. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8713 12. https://www.wireshark.org/security/wnpa-sec-2014-23.html 13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10596 14. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8714 15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10462 16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10463 17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10469 18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10470 19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10547 20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10576 21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10577 22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10578 23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10611 24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10619 25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10622 26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10624 27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10625 28. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10626 29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10629 30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10630 31. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10651 32. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10676 33. http://www.wireshark.org/download.html 34. http://www.wireshark.org/download.html#thirdparty 35. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419 36. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516 37. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814 38. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234 39. https://wiki.wireshark.org/Development/Win64 40. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9044 41. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3528 42. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035 43. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056 44. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357 45. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4445 46. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985 47. http://ask.wireshark.org/ 48. http://www.wireshark.org/lists/ 49. http://www.wiresharktraining.com/ 50. http://www.wireshark.org/faq.html Digests wireshark-1.10.11.tar.bz2: 26857388 bytes MD5(wireshark-1.10.11.tar.bz2)=3696b172ced999a82559fe6145865cb1 SHA1(wireshark-1.10.11.tar.bz2)=f8c75b65d79fc597a7a2468cf01d4e3061997ebf RIPEMD160(wireshark-1.10.11.tar.bz2)=85a0752554cd5911faf1072bb8f99d401680c9f4 Wireshark-win64-1.10.11.exe: 28030736 bytes MD5(Wireshark-win64-1.10.11.exe)=f3cce383e3643de23f3068076297d87a SHA1(Wireshark-win64-1.10.11.exe)=cc58ac1ab31e76f84fa7055dc4c05f68f942abff RIPEMD160(Wireshark-win64-1.10.11.exe)=d3f4fbde104c014a0cdaef7ab5a93006de3883e4 Wireshark-win32-1.10.11.exe: 22180976 bytes MD5(Wireshark-win32-1.10.11.exe)=fdc737a71d3df0458779be1d7372ebcf SHA1(Wireshark-win32-1.10.11.exe)=4d17422d8c8fba7a6e5b69baebfc98047d8b01df RIPEMD160(Wireshark-win32-1.10.11.exe)=90b14b4bb33a70e7898685f8dc8c3a83f84dad8c Wireshark-1.10.11.u3p: 30675970 bytes MD5(Wireshark-1.10.11.u3p)=62947eb63d809b46caf5da78486f7b7d SHA1(Wireshark-1.10.11.u3p)=e82f4ec1e5f05d80b3c91a732efffcaf91efdc26 RIPEMD160(Wireshark-1.10.11.u3p)=d1bed63df846e3d7191f284513ec0b068f9a4bca WiresharkPortable-1.10.11.paf.exe: 23550240 bytes MD5(WiresharkPortable-1.10.11.paf.exe)=9df57f5438467ab5b670a9492b0b2106 SHA1(WiresharkPortable-1.10.11.paf.exe)=fbcaa0a441c79d9f6d399cd37c0a185cb80acd02 RIPEMD160(WiresharkPortable-1.10.11.paf.exe)=5ceaa28c236f3f957ca01acb5209cafbbb04acd7 Wireshark 1.10.11 Intel 64.dmg: 24803914 bytes MD5(Wireshark 1.10.11 Intel 64.dmg)=5df3cd80daf050f16d580f07e7361880 SHA1(Wireshark 1.10.11 Intel 64.dmg)=ac8fbdaacc6aefac5f7e7322ca98a7d854305393 RIPEMD160(Wireshark 1.10.11 Intel 64.dmg)=ffb99ee71abff92f45c5fb21643952748f2a18d2 Wireshark 1.10.11 Intel 32.dmg: 20471182 bytes MD5(Wireshark 1.10.11 Intel 32.dmg)=0537ac13aceca4da1016ff9baba7591f SHA1(Wireshark 1.10.11 Intel 32.dmg)=af7698d561694d9043bd356977cf445d52abdfaa RIPEMD160(Wireshark 1.10.11 Intel 32.dmg)=5d646f0e38c1d6c45b0a25f26be8c0c05bc30ca7 patch-wireshark-1.10.10-to-1.10.11.bz2: 104945 bytes MD5(patch-wireshark-1.10.10-to-1.10.11.bz2)=2cf1f28b72e2ab7cf77346b652107d20 SHA1(patch-wireshark-1.10.10-to-1.10.11.bz2)=30f1dba5b2cc64d6bd98ac69ef4b903620e0bcc2 RIPEMD160(patch-wireshark-1.10.10-to-1.10.11.bz2)=39c8c564b1353dbfc79ca6319fe7f4f2b1f246f6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRjxCcACgkQpw8IXSHylJqYjACfVxUh/K1VCjPf9fy0H2LMCbkD a6QAoIPgWlF06QxRg9V53dUGcBx3tSgC =hFOb -----END PGP SIGNATURE-----
- Prev by Date: [Wireshark-users] Wireshark 1.12.2 is now available
- Next by Date: [Wireshark-users] How does wireshark know which is the http response for a given request?
- Previous by thread: [Wireshark-users] Wireshark 1.12.2 is now available
- Next by thread: [Wireshark-users] How does wireshark know which is the http response for a given request?
- Index(es):