In Wireshark 3.0.0 to 3.0.1, 2.6.0 to 2.6.8, and 2.4.0 to 2.4.14, the dissection engine could crash. This was addressed in epan/packet.c by restricting the number of layers and consequently limiting recursion.

Several vulnerabilities were fixed in the Wireshark network protocol analyzer.

CVE-2019-10894

GSS-API dissector crash

CVE-2019-10895

NetScaler file parser crash

CVE-2019-10896

DOF dissector crash

CVE-2019-10899

SRVLOC dissector crash

CVE-2019-10901

LDSS dissector crash

CVE-2019-10903

DCERPC SPOOLSS dissector crash

CVE-2019-12295

Dissection engine could crash

For Debian 9 stretch, these problems have been fixed in version 2.6.8-1.1~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.

In Wireshark 3.0.0 to 3.0.1, 2.6.0 to 2.6.8, and 2.4.0 to 2.4.14, the dissection engine could crash. This was addressed in epan/packet.c by restricting the number of layers and consequently limiting recursion.
(CVE-2019-12295)

Impact

An attacker can leverage this issue to stop the affected application and deny service to legitimate users.

It was discovered that Wireshark improperly handled certain input. A remote or local attacker could cause Wireshark to crash by injecting malformed packets onto the wire or convincing someone to read a malformed packet trace file.

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. 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 prior to 3.0.2. It is, therefore, affected by a flaw in the dissection engine which 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.

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.0.2. It is, therefore, affected by a flaw in the dissection engine which 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.

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 2.6.9. It is, therefore, affected by a flaw in the dissection engine which 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.

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 2.6.9. It is, therefore, affected by a flaw in the dissection engine which 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.

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 2.4.15. It is, therefore, affected by a flaw in the dissection engine which 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.

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 2.4.15. It is, therefore, affected by a flaw in the dissection engine which 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.

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
142153	Debian DLA-2423-1 : wireshark security update	Nessus	Debian Local Security Checks	high
138229	F5 Networks BIG-IP : Wireshark vulnerability (K06725231)	Nessus	F5 Networks Local Security Checks	high
128875	Ubuntu 16.04 LTS / 18.04 LTS : Wireshark vulnerabilities (USN-4133-1)	Nessus	Ubuntu Local Security Checks	high
125369	Wireshark 3.0.x < 3.0.2 A Vulnerability	Nessus	Windows	high
125368	Wireshark 3.0.x < 3.0.2 A Vulnerability (macOS)	Nessus	MacOS X Local Security Checks	high
125367	Wireshark 2.6.x < 2.6.9 A Vulnerability	Nessus	Windows	high
125366	Wireshark 2.6.x < 2.6.9 A Vulnerability (macOS)	Nessus	MacOS X Local Security Checks	high
125365	Wireshark 2.4.x < 2.4.15 A Vulnerability	Nessus	Windows	high
125364	Wireshark 2.4.x < 2.4.15 A Vulnerability (macOS)	Nessus	MacOS X Local Security Checks	high

Detections

Analytics

CVE-2019-12295

high

Tenable Plugins

high

high

high

high

high

high

high

high

high