In Wireshark 3.2.0 to 3.2.7, the GQUIC dissector could crash. This was addressed in epan/dissectors/packet-gquic.c by correcting the implementation of offset advancement.

The remote Redhat Enterprise Linux 8 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - wireshark: free operation on an uninitialized memory address in wiretap/netmon.c (CVE-2018-6836)

  - In Wireshark 2.4.0 to 2.4.3 and 2.2.0 to 2.2.11, the IxVeriWave file parser could crash. This was     addressed in wiretap/vwr.c by correcting the signature timestamp bounds checks. (CVE-2018-5334)

  - In Wireshark 2.4.0 to 2.4.3 and 2.2.0 to 2.2.11, the WCP dissector could crash. This was addressed in     epan/dissectors/packet-wcp.c by validating the available buffer length. (CVE-2018-5335)

  - In Wireshark 2.4.0 to 2.4.3 and 2.2.0 to 2.2.11, the JSON, XML, NTP, XMPP, and GDB dissectors could crash.
    This was addressed in epan/tvbparse.c by limiting the recursion depth. (CVE-2018-5336)

  - In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the GSS-API dissector could crash. This was     addressed in epan/dissectors/packet-gssapi.c by ensuring that a valid dissector is called.
    (CVE-2019-10894)

  - In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the NetScaler file parser could crash. This was     addressed in wiretap/netscaler.c by improving data validation. (CVE-2019-10895)

  - In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the DOF dissector could crash. This was addressed     in epan/dissectors/packet-dof.c by properly handling generated IID and OID bytes. (CVE-2019-10896)

  - In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the SRVLOC dissector could crash. This was     addressed in epan/dissectors/packet-srvloc.c by preventing a heap-based buffer under-read.
    (CVE-2019-10899)

  - In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the LDSS dissector could crash. This was     addressed in epan/dissectors/packet-ldss.c by handling file digests properly. (CVE-2019-10901)

  - In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the DCERPC SPOOLSS dissector could crash. This     was addressed in epan/dissectors/packet-dcerpc-spoolss.c by adding a boundary check. (CVE-2019-10903)

  - In Wireshark 3.0.0 to 3.0.2, 2.6.0 to 2.6.9, and 2.4.0 to 2.4.15, the ASN.1 BER dissector and related     dissectors could crash. This was addressed in epan/asn1.c by properly restricting buffer increments.
    (CVE-2019-13619)

  - In Wireshark 3.0.0 to 3.0.6 and 2.6.0 to 2.6.12, the CMS dissector could crash. This was addressed in     epan/dissectors/asn1/cms/packet-cms-template.c by ensuring that an object identifier is set to NULL after     a ContentInfo dissection. (CVE-2019-19553)

  - In Wireshark 2.6.0 to 2.6.5, the 6LoWPAN dissector could crash. This was addressed in     epan/dissectors/packet-6lowpan.c by avoiding use of a TVB before its creation. (CVE-2019-5716)

  - In Wireshark 2.6.0 to 2.6.5 and 2.4.0 to 2.4.11, the P_MUL dissector could crash. This was addressed in     epan/dissectors/packet-p_mul.c by rejecting the invalid sequence number of zero. (CVE-2019-5717)

  - In Wireshark 2.6.0 to 2.6.5 and 2.4.0 to 2.4.11, the RTSE dissector and other ASN.1 dissectors could     crash. This was addressed in epan/charsets.c by adding a get_t61_string length check. (CVE-2019-5718)

  - In Wireshark 2.6.0 to 2.6.5 and 2.4.0 to 2.4.11, the ISAKMP dissector could crash. This was addressed in     epan/dissectors/packet-isakmp.c by properly handling the case of a missing decryption data block.
    (CVE-2019-5719)

  - In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the TCAP dissector could crash. This was addressed in     epan/dissectors/asn1/tcap/tcap.cnf by avoiding NULL pointer dereferences. (CVE-2019-9208)

  - In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the ASN.1 BER and related dissectors could crash. This     was addressed in epan/dissectors/packet-ber.c by preventing a buffer overflow associated with excessive     digits in time values. (CVE-2019-9209)

  - In Wireshark 3.2.0 to 3.2.2, 3.0.0 to 3.0.9, and 2.6.0 to 2.6.15, the BACapp dissector could crash. This     was addressed in epan/dissectors/packet-bacapp.c by limiting the amount of recursion. (CVE-2020-11647)

  - In Wireshark 3.2.0 to 3.2.4, the GVCP dissector could go into an infinite loop. This was addressed in     epan/dissectors/packet-gvcp.c by ensuring that an offset increases in all situations. (CVE-2020-15466)

  - In Wireshark 3.2.0 to 3.2.6, 3.0.0 to 3.0.13, and 2.6.0 to 2.6.20, the TCP dissector could crash. This was     addressed in epan/dissectors/packet-tcp.c by changing the handling of the invalid 0xFFFF checksum.
    (CVE-2020-25862)

  - In Wireshark 3.2.0 to 3.2.6, 3.0.0 to 3.0.13, and 2.6.0 to 2.6.20, the MIME Multipart dissector could     crash. This was addressed in epan/dissectors/packet-multipart.c by correcting the deallocation of invalid     MIME parts. (CVE-2020-25863)

  - Memory leak in Kafka protocol dissector in Wireshark 3.4.0 and 3.2.0 to 3.2.8 allows denial of service via     packet injection or crafted capture file. (CVE-2020-26418)

  - In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite     loop. This was addressed in epan/dissectors/packet-fbzero.c by correcting the implementation of offset     advancement. (CVE-2020-26575)

  - In Wireshark 3.2.0 to 3.2.7, the GQUIC dissector could crash. This was addressed in     epan/dissectors/packet-gquic.c by correcting the implementation of offset advancement. (CVE-2020-28030)

  - Infinite loop in the RTMPT dissector in Wireshark 3.6.0 and 3.4.0 to 3.4.10 allows denial of service via     packet injection or crafted capture file (CVE-2021-4185)

  - Due to a failure in validating the length provided by an attacker-crafted CP2179 packet, Wireshark     versions 2.0.0 through 4.0.7 is susceptible to a divide by zero allowing for a denial of service attack.
    (CVE-2023-2906)

Note that Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

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.

New version 3.4.0. Security fix for CVE-2020-26575, CVE-2020-28030.

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 fixes the following issues :

wireshark was updated to 3.2.8 :

  - CVE-2020-26575: Fixed an issue where FBZERO dissector     was entering in infinite loop (bsc#1177406)

  - CVE-2020-28030: Fixed an issue where GQUIC dissector was     crashing (bsc#1178291)

  - Infinite memory allocation while parsing this tcp packet

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.

This update for wireshark fixes the following issues :

  - wireshark was updated to 3.2.8 :

  - CVE-2020-26575: Fixed an issue where FBZERO dissector     was entering in infinite loop (bsc#1177406)

  - CVE-2020-28030: Fixed an issue where GQUIC dissector was     crashing (bsc#1178291)

  - Infinite memory allocation while parsing this tcp packet

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

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

  - In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite     loop. This was addressed in epan/dissectors/packet-fbzero.c by correcting the implementation of offset     advancement. (CVE-2020-26575)

  - In Wireshark 3.2.0 to 3.2.7, the GQUIC dissector could crash. This was addressed in     epan/dissectors/packet-gquic.c by correcting the implementation of offset advancement. (CVE-2020-28030)

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

  - In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite     loop. This was addressed in epan/dissectors/packet-fbzero.c by correcting the implementation of offset     advancement. (CVE-2020-26575)

  - In Wireshark 3.2.0 to 3.2.7, the GQUIC dissector could crash. This was addressed in     epan/dissectors/packet-gquic.c by correcting the implementation of offset advancement. (CVE-2020-28030)

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
196737	RHEL 8 : wireshark (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	critical
146291	Debian DLA-2547-1 : wireshark security update	Nessus	Debian Local Security Checks	high
144175	Fedora 32 : 1:wireshark (2020-d4344dd12f)	Nessus	Fedora Local Security Checks	high
144163	Fedora 33 : 1:wireshark (2020-4cff262f07)	Nessus	Fedora Local Security Checks	high
143711	SUSE SLED15 / SLES15 Security Update : wireshark (SUSE-SU-2020:3376-1)	Nessus	SuSE Local Security Checks	high
143508	openSUSE Security Update : wireshark (openSUSE-2020-2107)	Nessus	SuSE Local Security Checks	high
143312	openSUSE Security Update : wireshark (openSUSE-2020-2076)	Nessus	SuSE Local Security Checks	high
142678	Wireshark 3.2.x < 3.2.8 Multiple Vulnerabilities	Nessus	Windows	high
142677	Wireshark 3.2.x < 3.2.8 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	high

Detections

Analytics

CVE-2020-28030

high

Tenable Plugins

critical

high

high

high

high

high

high

high

high