Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2020.1785
Multiple Wireshark releases
20 May 2020
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Wireshark
Publisher: Wireshark
Operating System: Windows
UNIX variants (UNIX, Linux, OSX)
Impact/Access: Denial of Service -- Unknown/Unspecified
Resolution: Patch/Upgrade
Original Bulletin:
https://www.wireshark.org/lists/wireshark-announce/202005/msg00000.html
https://www.wireshark.org/lists/wireshark-announce/202005/msg00001.html
https://www.wireshark.org/lists/wireshark-announce/202005/msg00002.html
Comment: This bulletin contains three (3) Wireshark security advisories.
- --------------------------BEGIN INCLUDED TEXT--------------------
Wireshark 2.6.17 is now available
I'm proud to announce the release of Wireshark 2.6.17.
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
o wnpa-sec-2020-08[1] The NFS dissector could crash. Bug 16476[2].
The following bugs have been fixed:
o PVS-Studio analyser long list of issues. Bug 16335[3].
o pcapng file dissector incorrectly computes nanoseconds from
timestamps because it assumes the resolution is in nanoseconds.
Bug 16440[4].
o Read of uninitialized memory in detect_camins_file. Bug 16458[5].
o Read of uninitialized memory in lanalyzer_read_trace_record. Bug
16459[6].
o capinfos "Capture duration" output is truncated if there are more
than 11 digits of seconds and fractions of a second. Bug
16519[7].
o MIME Files Format/pcapng: Simple Packet Block parsed incorrectly.
Bug 16526[8].
o Buildbot crash output: fuzz-2020-05-13-12195.pcap. Bug 16564[9].
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
AoE, APRS, ASN.1 BER, FTP, GSM SMS, Infiniband, ISObus VT, MAC LTE,
NFS, ONC RPC, OSC, pcapng, PDCP LTE, RADIUS, RLC LTE, SDP, SIP,
Snort, and STUN
New and Updated Capture File Support
Camins, Catapult DCT 2000, Lanalyzer, and MPEG
New and Updated Capture Interfaces support
There is no new or updated capture file 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[10] 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
The BER dissector might infinitely loop. Bug 1516[11].
Capture filters aren't applied when capturing from named pipes. Bug
1814[12].
Filtering tshark captures with read filters (-R) no longer works. Bug
2234[13].
Application crash when changing real-time option. Bug 4035[14].
Wireshark and TShark will display incorrect delta times in some cases.
Bug 4985[15].
Wireshark should let you work with multiple capture files. Bug
10488[16].
Getting Help
Community support is available on Wireshark's Q&A site[17] 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[18].
Frequently Asked Questions
A complete FAQ is available on the Wireshark web site[19].
Last updated 2020-05-19 18:38:34 UTC
References
1. https://www.wireshark.org/security/wnpa-sec-2020-08
2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16476
3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16335
4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16440
5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16458
6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16459
7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16519
8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16526
9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16564
10. https://www.wireshark.org/download.html#thirdparty
11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
17. https://ask.wireshark.org/
18. https://www.wireshark.org/lists/
19. https://www.wireshark.org/faq.html
Digests
wireshark-2.6.17.tar.xz: 28523700 bytes
SHA256(wireshark-2.6.17.tar.xz)=eb37fa54f35ca56fa3532d4cf391c0600e1d068f6c1503918024c553d8067eff
RIPEMD160(wireshark-2.6.17.tar.xz)=62e7d2bf5d76a13a22cd60dff7246b1989ac9e5d
SHA1(wireshark-2.6.17.tar.xz)=8bdf29a621b848a9d3ce368855077625cc01752e
Wireshark-win64-2.6.17.exe: 59709416 bytes
SHA256(Wireshark-win64-2.6.17.exe)=ede67647da0b1c103e9ce192dd91927c9931c0b277db812324166585e18fd09a
RIPEMD160(Wireshark-win64-2.6.17.exe)=42eace40cf314896b8535e5085d9b7171ab75ffb
SHA1(Wireshark-win64-2.6.17.exe)=2c3b66ace5bfd1c0e741940d9b3abafe5f967663
Wireshark-win32-2.6.17.exe: 54072136 bytes
SHA256(Wireshark-win32-2.6.17.exe)=b72fb88ecf385e23fdb028dcc66c623d5eeff03fc226b9735907355e44194d21
RIPEMD160(Wireshark-win32-2.6.17.exe)=a0f2905242f5f7afa8e951ae00ab50442dd16280
SHA1(Wireshark-win32-2.6.17.exe)=a9dedf08861fa5431745a30bbca25c4012c32ff2
Wireshark-win64-2.6.17.msi: 49172480 bytes
SHA256(Wireshark-win64-2.6.17.msi)=508b7b5372e8b086bebd628ffbe9be7525881515ebdb8b5e3fd8e956065517b8
RIPEMD160(Wireshark-win64-2.6.17.msi)=7dcc2def1739adcbede2fb4c0e72221eafbd73df
SHA1(Wireshark-win64-2.6.17.msi)=8e04d1e4b03a6ee102619af7be809f2fa35464f7
Wireshark-win32-2.6.17.msi: 43577344 bytes
SHA256(Wireshark-win32-2.6.17.msi)=bd4243fcb9becea3f05c71641cfc314718d59b3c96de4ca60f326b7b3198f00e
RIPEMD160(Wireshark-win32-2.6.17.msi)=916ebbfc94abd46a311f534035d62db63683878e
SHA1(Wireshark-win32-2.6.17.msi)=857f09180a299a9f18ff68ae24f0dbf758bdcd4e
WiresharkPortable_2.6.17.paf.exe: 37312512 bytes
SHA256(WiresharkPortable_2.6.17.paf.exe)=b8e2c12e43511f2febcdadf195ac5cb2c907f4b864b2824cec1884d40931006a
RIPEMD160(WiresharkPortable_2.6.17.paf.exe)=a0daced4dd3baad3f760cbcafcd52ddd803ff2f6
SHA1(WiresharkPortable_2.6.17.paf.exe)=8c735ab2e7128124f8138cf0860fc18b74977036
Wireshark 2.6.17 Intel 64.dmg: 108245045 bytes
SHA256(Wireshark 2.6.17 Intel 64.dmg)=b4d428a54b0acd1f7231f581ee5ae7c7556d160b417f4996a432933a66edc92c
RIPEMD160(Wireshark 2.6.17 Intel 64.dmg)=fd9c2d420dce19a0bbffbc4bb40483145f7c0f11
SHA1(Wireshark 2.6.17 Intel 64.dmg)=8ba48729abef0515e60582093bd7a75fdf8504a5
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
- -------------------------------------------------------------------------------
Wireshark 3.0.11 is now available
I'm proud to announce the release of Wireshark 3.0.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
The Windows installers now ship with Qt 5.12.8. They previously
shipped with Qt 5.12.6.
Bug Fixes
The following vulnerabilities have been fixed:
o wnpa-sec-2020-08[1] The NFS dissector could crash. Bug 16476[2].
The following bugs have been fixed:
o PVS-Studio analyser long list of issues. Bug 16335[3].
o pcapng file dissector incorrectly computes nanoseconds from
timestamps because it assumes the resolution is in nanoseconds.
Bug 16440[4].
o Read of uninitialized memory in detect_camins_file. Bug 16458[5].
o Read of uninitialized memory in lanalyzer_read_trace_record. Bug
16459[6].
o Range parameter on numeric parameter in extcap plugin doesn't
work. Bug 16510[7].
o capinfos "Capture duration" output is truncated if there are more
than 11 digits of seconds and fractions of a second. Bug
16519[8].
o MIME Files Format/pcapng: Simple Packet Block parsed incorrectly.
Bug 16526[9].
o Buildbot crash output: fuzz-2020-05-13-12195.pcap. Bug 16564[10].
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
AoE, APRS, ASN.1 BER, FTP, GSM SMS, Infiniband, ISObus VT, MAC LTE,
NFS, ONC RPC, OSC, pcapng, PDCP LTE, SDP, SIP, Snort, STUN, and UMTS
FP
New and Updated Capture File Support
Camins, Catapult DCT 2000, Lanalyzer, and MPEG
New and Updated Capture Interfaces support
There is no new or updated capture file 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[11] 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.
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[12] 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[13].
Bugs and feature requests can be reported on the bug tracker[14].
Frequently Asked Questions
A complete FAQ is available on the Wireshark web site[15].
Last updated 2020-05-19 18:02:07 UTC
References
1. https://www.wireshark.org/security/wnpa-sec-2020-08
2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16476
3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16335
4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16440
5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16458
6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16459
7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16510
8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16519
9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16526
10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16564
11. https://www.wireshark.org/download.html#thirdparty
12. https://ask.wireshark.org/
13. https://www.wireshark.org/lists/
14. https://bugs.wireshark.org/
15. https://www.wireshark.org/faq.html
Digests
wireshark-3.0.11.tar.xz: 30887388 bytes
SHA256(wireshark-3.0.11.tar.xz)=ee04bf24e33f2b2868f3a311422996ff55373264d406b3672522c14c888429b0
RIPEMD160(wireshark-3.0.11.tar.xz)=695d542c1f2735f63e88b754ba8ba87ec2c9bbd6
SHA1(wireshark-3.0.11.tar.xz)=af905567619462641e351b2bc7f22334400dd958
Wireshark-win32-3.0.11.exe: 54044416 bytes
SHA256(Wireshark-win32-3.0.11.exe)=c49459b98ae24ffb5b214b5979838bd8ed5458922d33dadfbad37d8c8654d929
RIPEMD160(Wireshark-win32-3.0.11.exe)=6347a256c2503c39d221ec95f70a85f01a4da4c9
SHA1(Wireshark-win32-3.0.11.exe)=81c84f726127ee2a1a231a9c00d2a3edda82f26e
Wireshark-win64-3.0.11.exe: 59262736 bytes
SHA256(Wireshark-win64-3.0.11.exe)=5ba8cf51a0894b447ce4e1f562313818035641c7694662d2622fb406e1971abb
RIPEMD160(Wireshark-win64-3.0.11.exe)=d7d7564003fa50039f2c830629374bdff93a7c18
SHA1(Wireshark-win64-3.0.11.exe)=61b7e3a007396b2e6b1bd655ba8bc42c6b9f3efc
Wireshark-win32-3.0.11.msi: 42020864 bytes
SHA256(Wireshark-win32-3.0.11.msi)=8ace795b35dee007061e97a05c48bc131915860a4f24afa35e5cac808bdcdc79
RIPEMD160(Wireshark-win32-3.0.11.msi)=e75e28db06b3648be5c6585c2c83c8d98290ec78
SHA1(Wireshark-win32-3.0.11.msi)=dd476a033f7d7565c08edc19cab458f620ad38fa
Wireshark-win64-3.0.11.msi: 47230976 bytes
SHA256(Wireshark-win64-3.0.11.msi)=4cd8ec47374f498cefcc14e1a5930aff59418743f234498bb5c09cfadf3ddbb1
RIPEMD160(Wireshark-win64-3.0.11.msi)=7fdb8bbeb931cfacaca916dba76e1aed257a8bb1
SHA1(Wireshark-win64-3.0.11.msi)=c78431b56c96677d7e28a233b9dd3488f621a21b
WiresharkPortable_3.0.11.paf.exe: 35810248 bytes
SHA256(WiresharkPortable_3.0.11.paf.exe)=83c0a70729cf24c34ba08277c4f6b846bcda77e75c8a639cd5030daa0c767b28
RIPEMD160(WiresharkPortable_3.0.11.paf.exe)=97de551c9100c4ecad284e933b7297dd53c1ab83
SHA1(WiresharkPortable_3.0.11.paf.exe)=f418f29f714e639146df8f155c7bb4cbd54599de
Wireshark 3.0.11 Intel 64.dmg: 93102152 bytes
SHA256(Wireshark 3.0.11 Intel 64.dmg)=c382859ef7fc465e525d890b02ceff9d42fee0fd835d9d7caa80e3fdec9c4b1a
RIPEMD160(Wireshark 3.0.11 Intel 64.dmg)=06de7690f1f0a8754745a0e4e6829e85b2416662
SHA1(Wireshark 3.0.11 Intel 64.dmg)=00d869f9b406ee8c628ecdcbe1e09d52787fe18b
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
- -------------------------------------------------------------------------------
Wireshark 3.2.4 is now available
I'm proud to announce the release of Wireshark 3.2.4.
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
The Windows installers now ship with Qt 5.12.8. They previously
shipped with Qt 5.12.6.
The Windows installers now ship with Npcap 0.9991 They previously
shipped with Npcap 0.9989
Bug Fixes
The following vulnerabilities have been fixed:
o wnpa-sec-2020-08[1] The NFS dissector could crash. Bug 16476[2].
The following bugs have been fixed:
o SDP dissector does not parse sprop-parameter-sets field. Bug
16322[3].
o PVS-Studio analyser long list of issues. Bug 16335[4].
o Can't have duplicate personal and global profile names. Bug
16423[5].
o pcapng file dissector incorrectly computes nanoseconds from
timestamps because it assumes the resolution is in nanoseconds.
Bug 16440[6].
o Read of uninitialized memory in detect_camins_file. Bug 16458[7].
o Read of uninitialized memory in lanalyzer_read_trace_record. Bug
16459[8].
o capture -> options -> select interface -> (choose) -> SEGV. Bug
16489[9].
o SOMEIP: SOME/IP dissector ignores the length field configuration
of structs. Bug 16490[10].
o Packet List Pane doesn't consume the entire pane. Bug 16491[11].
o Range parameter on numeric parameter in extcap plugin doesn't
work. Bug 16510[12].
o Export Packet Dissections not working on Windows (Wireshark
3.2.x). Bug 16516[13].
o capinfos "Capture duration" output is truncated if there are more
than 11 digits of seconds and fractions of a second. Bug
16519[14].
o MIME Files Format/pcapng: Simple Packet Block parsed incorrectly.
Bug 16526[15].
o SOMEIP: SOME/IP-SD unique id is not unique for eventgroup types
(BUG). Bug 16549[16].
o Buildbot crash output: fuzz-2020-05-13-12195.pcap. Bug 16564[17].
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
AoE, APRS, ASN.1 BER, DIS, DTLS, FTP, GSM SMS, H.264, IMAP,
Infiniband, ISObus VT, Kafka, LSD, MAC LTE, NAS 5GS, NFS, ONC RPC,
OSC, pcapng, PDCP LTE, RADIUS, RLC LTE, RTSP, SDP, SIP, Snort,
SOMEIP, STUN, TLS, and UMTS FP
New and Updated Capture File Support
Camins, Catapult DCT 2000, Lanalyzer, and MPEG
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[18] 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.
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[19] 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[20].
Bugs and feature requests can be reported on the bug tracker[21].
Frequently Asked Questions
A complete FAQ is available on the Wireshark web site[22].
Last updated 2020-05-19 17:45:44 UTC
References
1. https://www.wireshark.org/security/wnpa-sec-2020-08
2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16476
3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16322
4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16335
5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16423
6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16440
7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16458
8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16459
9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16489
10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16490
11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16491
12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16510
13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16516
14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16519
15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16526
16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16549
17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16564
18. https://www.wireshark.org/download.html#thirdparty
19. https://ask.wireshark.org/
20. https://www.wireshark.org/lists/
21. https://bugs.wireshark.org/
22. https://www.wireshark.org/faq.html
Digests
wireshark-3.2.4.tar.xz: 31580440 bytes
SHA256(wireshark-3.2.4.tar.xz)=d17d461e849e2d0b033431c45f71d8ee8ec3c8faa232a6ad63069a47927db8aa
RIPEMD160(wireshark-3.2.4.tar.xz)=5dccf5ba44dd8f6c275b74ab07137ce80f4ab76d
SHA1(wireshark-3.2.4.tar.xz)=bb4157b57c1bcdbac948a1282dafad027d57be9b
Wireshark-win32-3.2.4.exe: 54867824 bytes
SHA256(Wireshark-win32-3.2.4.exe)=c17e4a812031d5dfd4ef0a4b4dae1b60bb45eb7ce8c9e8b1b5eff4db5bcf4b72
RIPEMD160(Wireshark-win32-3.2.4.exe)=3ac743c96a4b1e9e006501e45b1a8f398d54d511
SHA1(Wireshark-win32-3.2.4.exe)=ea4cc781339618eb16db4fdc96c413f119229ef3
Wireshark-win64-3.2.4.exe: 60037848 bytes
SHA256(Wireshark-win64-3.2.4.exe)=db2565ee6410b7c57f54aaac86954e4f6a98e2ea31ffbea83e60b981fff57301
RIPEMD160(Wireshark-win64-3.2.4.exe)=e058bfdb62c1b0392d39c80d24e7f001587ed907
SHA1(Wireshark-win64-3.2.4.exe)=32c0cea3623db22eb7f0dbf24ac4902a4e873f3d
Wireshark-win32-3.2.4.msi: 43028480 bytes
SHA256(Wireshark-win32-3.2.4.msi)=a614bdb63e9dfa1150cdcb471790ebe32f1c8a269079cbccab6ece4ad7700575
RIPEMD160(Wireshark-win32-3.2.4.msi)=7431e01c63b522ad59f1adb58fa0da7e5b12362b
SHA1(Wireshark-win32-3.2.4.msi)=22ca61d51e9d66e198769225fbbc0bfc2f3a0f76
Wireshark-win64-3.2.4.msi: 48283648 bytes
SHA256(Wireshark-win64-3.2.4.msi)=eb13bc841c98c398a7f26705f3621ac4ffe90fc158f4ea48db3ba56968a0d41b
RIPEMD160(Wireshark-win64-3.2.4.msi)=33e2f498e1919a11b1c20cb125af30c304534cc8
SHA1(Wireshark-win64-3.2.4.msi)=4e2aeab60879518b5d9a81d8449874db23ad4dc6
WiresharkPortable_3.2.4.paf.exe: 36581616 bytes
SHA256(WiresharkPortable_3.2.4.paf.exe)=2c8ea4e6776a334d43909c53d7c656db10ad425beec5fe927b8d1fb0467309da
RIPEMD160(WiresharkPortable_3.2.4.paf.exe)=759413437b7b91efe28eab3c6120530421ada774
SHA1(WiresharkPortable_3.2.4.paf.exe)=6c0f29f5554b0ee7160b21f7a6c6a5069161e266
Wireshark 3.2.4 Intel 64.dmg: 97572886 bytes
SHA256(Wireshark 3.2.4 Intel 64.dmg)=735d43bdbde1caeb9bfff89acc62acfeb05ffda36e6d0d243bc08333e60fdac6
RIPEMD160(Wireshark 3.2.4 Intel 64.dmg)=672b26161f45f015fff6d16d96570b85f59c0bcb
SHA1(Wireshark 3.2.4 Intel 64.dmg)=5a550cae3e5cc02441f39df2fdb84edb525d5b87
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
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
https://www.auscert.org.au/bulletins/
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQIVAwUBXsSz7ONLKJtyKPYoAQi05RAAqu8oBsvR27PouNQfxU1NHOn8kVgVb1WW
t4lOhIEmdBuULtzQbfrlBYa4dw1AJf0HknDMME6LwatFXraxy033idXSDVzJFt1I
GirjJrbSE8AvkaRRA32qZ2ZoL0n3xZb43xXj/xWRNcKfAQ+KmYhCDOJHC59Sq2nL
QvAr7L74q0tMg+8JBh+AcEsjPFBOBXR+QIo34Yrd+Jxh2v9N2WCgIry1HyEu9CwY
ZwLhLSOto7FN85L2cCj80QE+ePm+po1GL7bhy6XeSrS8Ayuy2Ph2ycH4P12y26ge
7SL5IpId5+DLhicfIOFRInZYv2tva0VzWiuDUU4qaLL6KjboplZT4/QSRgK6w5V6
31CbZ+go3lZgKithya29RzGdFPYlvK8+In864lYRiih4tntH5Yva+4gORY4Ja6B7
aLxQ54R2ggMqMjj3ZibvUB62xNIQCFsgw4ffp9NBC0yh+RaVngLzSKhFOiAVVsSb
DETGjHkFJ/BBi31l2i7j1qHwR7sSRRz/gcNiMGj40lhyHlYAjOacmUNEjmBDicUk
KiuFuNl05pPE3nHqBD7Yc64wkshUjcktLKl+2RtsKjDx+IQ8ZnGs8Uo+zBj389cD
7wtMvxB/CBLHEy13T0UY845VAtbJyuI97o7Ua2nANU5qAus51PJ4Wy85nTlu4Efr
NuVQty+jo1w=
=SHhE
-----END PGP SIGNATURE-----