3.2.3

----

New version 3.2.2 Security fix for CVE-2020-7044, CVE-2020-9428, CVE-2020-9430, CVE-2020-9431

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.

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.

The remote host is affected by the vulnerability described in GLSA-202007-13 (Wireshark: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Wireshark. Please       review the CVE identifiers referenced below for details.
  Impact :

    Please review the referenced CVE identifiers for details.
  Workaround :

    There is no known workaround at this time.

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

  - The LTE RRC dissector could leak memory. 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. (wireshark-bug-16341) (CVE-2020-9431)

  - The WiMax DLMAP 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. (wireshark-     bug-16368) (CVE-2020-9430)

  - The EAP 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. (wireshark-bug-16397)     (CVE-2020-9428)

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

Several vulnerabilities were fixed in Wireshark, a network sniffer.

CVE-2019-13619

ASN.1 BER and related dissectors crash.

CVE-2019-16319

The Gryphon dissector could go into an infinite loop.

CVE-2019-19553

The CMS dissector could crash.

CVE-2020-7045

The BT ATT dissector could crash.

CVE-2020-9428

The EAP dissector could crash.

CVE-2020-9430

The WiMax DLMAP dissector could crash.

CVE-2020-9431

The LTE RRC dissector could leak memory.

CVE-2020-11647

The BACapp dissector could crash.

CVE-2020-13164

The NFS dissector could crash.

CVE-2020-15466

The GVCP dissector could go into an infinite loop.

CVE-2020-25862

The TCP dissector could crash.

CVE-2020-25863

The MIME Multipart dissector could crash.

CVE-2020-26418

Memory leak in the Kafka protocol dissector.

CVE-2020-26421

Crash in USB HID protocol dissector.

CVE-2020-26575

The Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite loop.

CVE-2020-28030

The GQUIC dissector could crash.

For Debian 9 stretch, these problems have been fixed in version 2.6.20-0+deb9u1.

We recommend that you upgrade your wireshark packages.

For the detailed security status of wireshark please refer to its security tracker page at:
https://security-tracker.debian.org/tracker/wireshark

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

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.

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

  - The LTE RRC dissector could leak memory. 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. (wireshark-bug-16341)

  - The WiMax DLMAP 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. (wireshark-     bug-16368)

  - The EAP 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. (wireshark-bug-16397)

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

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In Wireshark 3.2.0 to 3.2.1, 3.0.0 to 3.0.8, and 2.6.0 to 2.6.14, the EAP dissector could crash. This was     addressed in epan/dissectors/packet-eap.c by using more careful sscanf parsing. (CVE-2020-9428)

Note that Nessus relies on the presence of the package as reported by the vendor.

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

  - The LTE RRC dissector could leak memory. 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. (wireshark-bug-16341)

  - The WiMax DLMAP 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. (wireshark-     bug-16368)

  - The EAP 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. (wireshark-bug-16397)

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 Windows host is prior to 3.0.9. It is, therefore, affected by multiple vulnerabilities as referenced in the wireshark-3.0.9 advisory.

  - The LTE RRC dissector could leak memory. 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. (wireshark-bug-16341)

  - The WiMax DLMAP 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. (wireshark-     bug-16368)

  - The EAP 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. (wireshark-bug-16397)

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 prior to 3.2.2. It is, therefore, affected by multiple vulnerabilities as referenced in the wireshark-3.2.2 advisory.

  - The LTE RRC dissector could leak memory. 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. (wireshark-bug-16341)

  - The WiMax DLMAP 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. (wireshark-     bug-16368)

  - The EAP 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. (wireshark-bug-16397)

  - The WireGuard 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. (wireshark-bug-16394)

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 Windows host is prior to 3.2.2. It is, therefore, affected by multiple vulnerabilities as referenced in the wireshark-3.2.2 advisory.

  - The LTE RRC dissector could leak memory. 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. (wireshark-bug-16341)

  - The WiMax DLMAP 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. (wireshark-     bug-16368)

  - The EAP 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. (wireshark-bug-16397)

  - The WireGuard 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. (wireshark-bug-16394)

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	Published	Updated	Severity
135994	Fedora 31 : 1:wireshark (2020-87737529a4)	Nessus	Fedora Local Security Checks	4/27/2020	3/14/2024	high
134625	SUSE SLED15 / SLES15 Security Update : wireshark (SUSE-SU-2020:0693-1)	Nessus	SuSE Local Security Checks	3/16/2020	3/21/2024	high
138936	GLSA-202007-13 : Wireshark: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	7/27/2020	2/28/2024	high
134114	Wireshark 2.6.x < 2.6.15 Multiple Vulnerabilities	Nessus	Windows	2/28/2020	3/25/2024	high
146291	Debian DLA-2547-1 : wireshark security update	Nessus	Debian Local Security Checks	2/8/2021	1/23/2024	high
134755	openSUSE Security Update : wireshark (openSUSE-2020-362)	Nessus	SuSE Local Security Checks	3/20/2020	3/21/2024	high
134113	Wireshark 2.6.x < 2.6.15 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	2/28/2020	4/30/2025	high
223618	Linux Distros Unpatched Vulnerability : CVE-2020-9428	Nessus	Misc.	3/4/2025	3/4/2025	high
135997	Fedora 30 : 1:wireshark (2020-da7dcee2ec)	Nessus	Fedora Local Security Checks	4/27/2020	3/14/2024	high
134109	Wireshark 3.0.x < 3.0.9 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	2/28/2020	4/30/2025	high
134110	Wireshark 3.0.x < 3.0.9 Multiple Vulnerabilities	Nessus	Windows	2/28/2020	4/30/2025	high
134111	Wireshark 3.2.x < 3.2.2 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	2/28/2020	4/30/2025	high
134112	Wireshark 3.2.x < 3.2.2 Multiple Vulnerabilities	Nessus	Windows	2/28/2020	4/30/2025	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high

high

high

high

high

high

high