In Wireshark 3.0.0, the GSUP dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-gsm_gsup.c by rejecting an invalid Information Element length.

This update for wireshark and libmaxminddb fixes the following issues :

Update wireshark to new major version 3.2.2 and introduce libmaxminddb for GeoIP support (bsc#1156288).

New features include :

  - Added support for 111 new protocols, including     WireGuard, LoRaWAN, TPM 2.0, 802.11ax and QUIC

  - Improved support for existing protocols, like HTTP/2

  - Improved analytics and usability functionalities

This update was imported from the SUSE:SLE-15:Update update project.

This update for wireshark and libmaxminddb fixes the following issues :

Update wireshark to new major version 3.2.2 and introduce libmaxminddb for GeoIP support (bsc#1156288).

New features include :

Added support for 111 new protocols, including WireGuard, LoRaWAN, TPM 2.0, 802.11ax and QUIC

Improved support for existing protocols, like HTTP/2

Improved analytics and usability functionalities

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

New version 3.0.1

Security fix for CVE-2019-10894, CVE-2019-10895, CVE-2019-10896, CVE-2019-10897, CVE-2019-10898, CVE-2019-10899, CVE-2019-10900, CVE-2019-10901, CVE-2019-10902, CVE-2019-10903

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The version of Wireshark installed on the remote Windows host is 3.0.x prior to 3.0.1. It is, therefore, affected by multiple vulnerabilities as referenced in the wireshark-3.0.1 advisory:

  - The NetScaler file parser could crash. It may be possible to make Wireshark crash by injecting a malformed     packet onto the wire or by convincing someone to read a malformed packet trace file. (CVE-2019-10895)

  - The SRVLOC dissector could crash. It may be possible to make Wireshark crash by injecting a malformed     packet onto the wire or by convincing someone to read a malformed packet trace file. (CVE-2019-10899)

  - The IEEE 802.11 dissector could go into an infinite loop. It may be possible to make Wireshark consume     excessive CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a     malformed packet trace file. (CVE-2019-10897)

  - The GSUP dissector could go into an infinite loop. It may be possible to make Wireshark consume excessive     CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a malformed     packet trace file. (CVE-2019-10898)

  - The Rbm dissector could go into an infinite loop. It may be possible to make Wireshark consume excessive     CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a malformed     packet trace file. (CVE-2019-10900)

  - The GSS-API dissector could crash. It may be possible to make Wireshark crash by injecting a malformed     packet onto the wire or by convincing someone to read a malformed packet trace file. (CVE-2019-10894)

  - The DOF dissector could crash. It may be possible to make Wireshark crash by injecting a malformed packet     onto the wire or by convincing someone to read a malformed packet trace file. (CVE-2019-10896)

  - The TSDNS dissector could crash. It may be possible to make Wireshark crash by injecting a malformed packet     onto the wire or by convincing someone to read a malformed packet trace file. (CVE-2019-10902)

  - The LDSS dissector could crash. It may be possible to make Wireshark crash by injecting a malformed packet     onto the wire or by convincing someone to read a malformed packet trace file. (CVE-2019-10901)

  - The DCERPC SPOOLSS dissector could crash. It may be possible to make Wireshark crash by injecting     a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.
    (CVE-2019-10903)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of Wireshark installed on the remote macOS / Mac OS X host is 3.0.x prior to 3.0.1. It is, therefore, affected by multiple vulnerabilities as referenced in the wireshark-3.0.1 advisory:

  - The NetScaler file parser could crash. It may be possible to make Wireshark crash by injecting a malformed     packet onto the wire or by convincing someone to read a malformed packet trace file. (CVE-2019-10895)

  - The SRVLOC dissector could crash. It may be possible to make Wireshark crash by injecting a malformed     packet onto the wire or by convincing someone to read a malformed packet trace file. (CVE-2019-10899)

  - The IEEE 802.11 dissector could go into an infinite loop. It may be possible to make Wireshark consume     excessive CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a     malformed packet trace file. (CVE-2019-10897)

  - The GSUP dissector could go into an infinite loop. It may be possible to make Wireshark consume excessive     CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a malformed     packet trace file. (CVE-2019-10898)

  - The Rbm dissector could go into an infinite loop. It may be possible to make Wireshark consume excessive     CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a malformed     packet trace file. (CVE-2019-10900)

  - The GSS-API dissector could crash. It may be possible to make Wireshark crash by injecting a malformed     packet onto the wire or by convincing someone to read a malformed packet trace file. (CVE-2019-10894)

  - The DOF dissector could crash. It may be possible to make Wireshark crash by injecting a malformed packet     onto the wire or by convincing someone to read a malformed packet trace file. (CVE-2019-10896)

  - The TSDNS dissector could crash. It may be possible to make Wireshark crash by injecting a malformed packet     onto the wire or by convincing someone to read a malformed packet trace file. (CVE-2019-10902)

  - The LDSS dissector could crash. It may be possible to make Wireshark crash by injecting a malformed packet     onto the wire or by convincing someone to read a malformed packet trace file. (CVE-2019-10901)

  - The DCERPC SPOOLSS dissector could crash. It may be possible to make Wireshark crash by injecting     a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.
    (CVE-2019-10903)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
134755	openSUSE Security Update : wireshark (openSUSE-2020-362)	Nessus	SuSE Local Security Checks	high
134625	SUSE SLED15 / SLES15 Security Update : wireshark (SUSE-SU-2020:0693-1)	Nessus	SuSE Local Security Checks	high
124530	Fedora 30 : 1:wireshark (2019-aef1dac6a0)	Nessus	Fedora Local Security Checks	high
124208	Fedora 29 : 1:wireshark (2019-77b2d840ef)	Nessus	Fedora Local Security Checks	high
124166	Wireshark 3.0.x < 3.0.1 Multiple Vulnerabilities	Nessus	Windows	high
124163	Wireshark 3.0.x < 3.0.1 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	high

Detections

Analytics

CVE-2019-10898

high

Tenable Plugins

high

high

high

high

high

high