In Wireshark 2.4.0, 2.2.0 to 2.2.8, and 2.0.0 to 2.0.14, the MSDP dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-msdp.c by adding length validation.

New version 2.4.2, fixes CVE-2017-15189, CVE-2017-15190, CVE-2017-15191, CVE-2017-15192, CVE-2017-15193, CVE-2017-13764, CVE-2017-13765, CVE-2017-13766, CVE-2017-13767

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 to version 2.2.11 fixes several issues.
These security issues were fixed :

  - CVE-2017-13767: The MSDP dissector could have gone into     an infinite loop. This was addressed by adding length     validation (bsc#1056248)

  - CVE-2017-13766: The Profinet I/O dissector could have     crash with an out-of-bounds write. This was addressed by     adding string validation (bsc#1056249)

  - CVE-2017-13765: The IrCOMM dissector had a buffer     over-read and application crash. This was addressed by     adding length validation (bsc#1056251)

  - CVE-2017-9766: PROFINET IO data with a high recursion     depth allowed remote attackers to cause a denial of     service (stack exhaustion) in the dissect_IODWriteReq     function (bsc#1045341)

  - CVE-2017-9617: Deeply nested DAAP data may have cause     stack exhaustion (uncontrolled recursion) in the     dissect_daap_one_tag function in the DAAP dissector     (bsc#1044417)

  - CVE-2017-15192: The BT ATT dissector could crash. This     was addressed in epan/dissectors/packet-btatt.c by     considering a case where not all of the BTATT packets     have the same encapsulation level. (bsc#1062645)

  - CVE-2017-15193: The MBIM dissector could crash or     exhaust system memory. This was addressed in     epan/dissectors/packet-mbim.c by changing the     memory-allocation approach. (bsc#1062645)

  - CVE-2017-15191: The DMP dissector could crash. This was     addressed in epan/dissectors/packet-dmp.c by validating     a string length. (bsc#1062645)

  - CVE-2017-17083: NetBIOS dissector could crash. This was     addressed in epan/dissectors/packet-netbios.c by     ensuring that write operations are bounded by the     beginning of a buffer. (bsc#1070727)

  - CVE-2017-17084: IWARP_MPA dissector could crash. This     was addressed in epan/dissectors/packet-iwarp-mpa.c by     validating a ULPDU length. (bsc#1070727)

  - CVE-2017-17085: the CIP Safety dissector could crash.
    This was addressed in epan/dissectors/packet-cipsafety.c     by validating the packet length. (bsc#1070727)

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 to version 2.2.9 fixes several issues. These security issues were fixed :

  - CVE-2017-13767: The MSDP dissector could have gone into     an infinite loop. This was addressed by adding length     validation (bsc#1056248).

  - CVE-2017-13766: The Profinet I/O dissector could have     crash with an out-of-bounds write. This was addressed by     adding string validation (bsc#1056249).

  - CVE-2017-13765: The IrCOMM dissector had a buffer     over-read and application crash. This was addressed by     adding length validation (bsc#1056251).

  - CVE-2017-9766: PROFINET IO data with a high recursion     depth allowed remote attackers to cause a denial of     service (stack exhaustion) in the dissect_IODWriteReq     function (bsc#1045341).

  - CVE-2017-9617: Deeply nested DAAP data may have cause     stack exhaustion (uncontrolled recursion) in the     dissect_daap_one_tag function in the DAAP dissector     (bsc#1044417).

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

Minor vulnerabilities that could be used to trigger dissector crashes, infinite loops, or cause excessive use of memory resources by making Wireshark read specially crafted packages from the network or a capture file :

  - CVE-2017-13767: MSDP dissector infinite loop     (boo#1056248)

  - CVE-2017-13766: Profinet I/O buffer overrun     (boo#1056249)

  - CVE-2017-13765: IrCOMM dissector buffer overrun     (boo#1056251)

  - Further bug fixes and updated protocol support as listed     in:
    https://www.wireshark.org/docs/relnotes/wireshark-2.2.9.
    html

The version of Wireshark installed on the remote Windows host is 2.4.x prior to 2.4.1. It is, therefore, affected by multiple denial of service vulnerabilities in the Modbus, IrCOMM, Profinet I/O, and MSDP dissectors. An unauthenticated, remote attacker can exploit this 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 these issues but has instead relied only on the application's self-reported version number.

The version of Wireshark installed on the remote Windows host is 2.2.x prior to 2.2.9. It is, therefore, affected by multiple denial of service vulnerabilities in the IrCOMM, Profinet I/O, and MSDP dissectors. An unauthenticated, remote attacker can exploit this 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 these issues but has instead relied only on the application's self-reported version number.

The version of Wireshark installed on the remote Windows host is 2.0.x prior to 2.0.15. It is, therefore, affected by multiple denial of service vulnerabilities in the IrCOMM and MSDP dissectors. An unauthenticated, remote attacker can exploit this 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 these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
105941	Fedora 27 : 1:wireshark (2017-9fd430dba0)	Nessus	Fedora Local Security Checks	high
105720	SUSE SLES11 Security Update : wireshark (SUSE-SU-2018:0054-1)	Nessus	SuSE Local Security Checks	high
103455	SUSE SLED12 / SLES12 Security Update : wireshark (SUSE-SU-2017:2555-1)	Nessus	SuSE Local Security Checks	high
102948	openSUSE Security Update : wireshark (openSUSE-2017-995)	Nessus	SuSE Local Security Checks	high
102921	Wireshark 2.4.x < 2.4.1 Multiple DoS	Nessus	Windows	high
102920	Wireshark 2.2.x < 2.2.9 Multiple DoS	Nessus	Windows	high
102919	Wireshark 2.0.x < 2.0.15 Multiple DoS	Nessus	Windows	high

Detections

Analytics

CVE-2017-13767

high

Tenable Plugins

high

high

high

high

high

high

high