101227

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14068

https://code.wireshark.org/review/23591

https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=8dbb21dfde14221dab09b6b9c7719b9067c1f06e

[debian-lts-announce] 20190115 [SECURITY] [DLA 1634-1] wireshark security update

https://www.wireshark.org/security/wnpa-sec-2017-44.html

Several issues in wireshark, a tool that captures and analyzes packets off the wire, have been found by different people. These are basically issues with length checks or invalid memory access in different dissectors. This could result in infinite loops or crashes by malicious packets.

For Debian 8 'Jessie', these problems have been fixed in version 1.12.1+g01b65bf-4+deb8u16.

We recommend that you upgrade your wireshark packages.

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 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.

wireshark developers reports :

In Wireshark 2.4.0 to 2.4.1, the DOCSIS dissector could go into an infinite loop. This was addressed in plugins/docsis/packet-docsis.c by adding decrements.

In Wireshark 2.4.0 to 2.4.1, the RTSP dissector could crash. This was addressed in epan/dissectors/packet-rtsp.c by correcting the scope of a variable.

In Wireshark 2.4.0 to 2.4.1, 2.2.0 to 2.2.9, and 2.0.0 to 2.0.15, the DMP dissector could crash. This was addressed in epan/dissectors/packet-dmp.c by validating a string length.

In Wireshark 2.4.0 to 2.4.1 and 2.2.0 to 2.2.9, 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.

In Wireshark 2.4.0 to 2.4.1 and 2.2.0 to 2.2.9, the MBIM dissector could crash or exhaust system memory. This was addressed in epan/dissectors/packet-mbim.c by changing the memory-allocation approach.

This update for wireshark fixes the following issues: Wireshark was updated to 2.2.10, fixing security issues and bugs :

  - CVE-2017-15191: DMP dissector crash (wnpa-sec-2017-44)

  - CVE-2017-15192: BT ATT dissector crash     (wnpa-sec-2017-42)

  - CVE-2017-15193: MBIM dissector crash (wnpa-sec-2017-43)

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.10 fixes multiple minor security issues.

These vulnerabilities that could be used to trigger dissector crashes or infinite loops by making Wireshark read specially crafted packages from the network or a capture file :

  - CVE-2017-15192: BT ATT dissector crash

  - CVE-2017-15193: MBIM dissector crash

  - CVE-2017-15191: DMP dissector crash

The version of Wireshark installed on the remote Windows host is 2.4.x prior to 2.4.2. It is, therefore, affected by multiple denial of service vulnerabilities in the DOCSIS, RTSP, DMP, BT ATT and MBIM 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.10. It is, therefore, affected by multiple denial of service vulnerabilities in the DMP, BT ATT and MBIM 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.16. It is, therefore, affected by a denial of service vulnerability in the DMP dissector. 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 MacOS/MacOSX host is 2.4.x prior to 2.4.2. It is, therefore, affected by multiple denial of service vulnerabilities in the DOCSIS, RTSP, DMP, BT ATT and MBIM 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 MacOS(X) host is 2.2.x prior to 2.2.10. It is, therefore, affected by multiple denial of service vulnerabilities in the DMP, BT ATT and MBIM 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 MacOS(X) host is 2.0.x prior to 2.0.16. It is, therefore, affected by a denial of service vulnerability in the DMP dissector. 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
121193	Debian DLA-1634-1 : wireshark security update	Nessus	Debian Local Security Checks	high
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
104265	FreeBSD : wireshark -- multiple security issues (4684a426-774d-4390-aa19-b8dd481c4c94)	Nessus	FreeBSD Local Security Checks	high
104210	SUSE SLED12 / SLES12 Security Update : wireshark (SUSE-SU-2017:2860-1)	Nessus	SuSE Local Security Checks	high
104073	openSUSE Security Update : wireshark (openSUSE-2017-1158)	Nessus	SuSE Local Security Checks	high
103986	Wireshark 2.4.x < 2.4.2 Multiple DoS	Nessus	Windows	high
103985	Wireshark 2.2.x < 2.2.10 Multiple DoS	Nessus	Windows	high
103984	Wireshark 2.0.x < 2.0.16 DMP dissector DoS	Nessus	Windows	medium
103983	Wireshark 2.4.x < 2.4.2 Multiple DoS (MacOS)	Nessus	MacOS X Local Security Checks	high
103982	Wireshark 2.2.x < 2.2.10 Multiple DoS (MacOS)	Nessus	MacOS X Local Security Checks	high
103981	Wireshark 2.0.x < 2.0.16 DMP dissector DoS (MacOS)	Nessus	MacOS X Local Security Checks	medium

CVE-2017-15191

Description

References

Details

Risk Information

CVSS v2.0

CVSS v3.0

Vulnerable Software

Configuration 1

Configuration 2

Tenable Plugins