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.

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - 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. (CVE-2017-15191)

  - 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. (CVE-2017-15192)

  - 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.
    (CVE-2017-15193)

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

  - 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.
    (CVE-2017-15193)

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

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - 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.
    (CVE-2017-15193)

  - In Wireshark 2.4.0, 2.2.0 to 2.2.8, and 2.0.0 to 2.0.14, the IrCOMM dissector has a buffer over-read and
    application crash. This was addressed in plugins/irda/packet-ircomm.c by adding length validation.
    (CVE-2017-13765)

  - In Wireshark 2.4.0 and 2.2.0 to 2.2.8, the Profinet I/O dissector could crash with an out-of-bounds write.
    This was addressed in plugins/profinet/packet-dcerpc-pn-io.c by adding string validation. (CVE-2017-13766)

  - 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. (CVE-2017-13767)

  - 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. (CVE-2017-15191)

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

  - 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.
    (CVE-2017-15193)

  - 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. (CVE-2017-15192)

  - 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. (CVE-2017-15191)

  - 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. (CVE-2017-15190)

  - 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. (CVE-2017-15189)

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

  - 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.
    (CVE-2017-15193)

  - 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. (CVE-2017-15192)

  - 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. (CVE-2017-15191)

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 / Mac OS X host is prior to 2.4.2. It is, therefore, affected by multiple vulnerabilities as referenced in the wireshark-2.4.2 advisory.

  - 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.
    (CVE-2017-15193)

  - 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. (CVE-2017-15192)

  - 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. (CVE-2017-15191)

  - 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. (CVE-2017-15190)

  - 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. (CVE-2017-15189)

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 / Mac OS X host is prior to 2.2.10. It is, therefore, affected by multiple vulnerabilities as referenced in the wireshark-2.2.10 advisory.

  - 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.
    (CVE-2017-15193)

  - 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. (CVE-2017-15192)

  - 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. (CVE-2017-15191)

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
427682	Alpine: multiple wireshark packages, tshark: security update to 2.2.10-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	high
427682	Alpine: multiple wireshark packages, tshark: security update to 2.2.10-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	high
220706	Linux Distros Unpatched Vulnerability : CVE-2017-15193	Nessus	Misc.	high
407635	Alpine: multiple wireshark packages, tshark: security update to 2.4.2-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	high
407635	Alpine: multiple wireshark packages, tshark: security update to 2.4.2-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	high
400798	Alpine: tshark, multiple wireshark packages: security update to 2.2.8-r0 (deprecated)	Tenable Cloud Security	Alpine Linux Local Security Checks	high
400798	Alpine: tshark, multiple wireshark packages: security update to 2.2.8-r0 (deprecated)	Tenable Self-Hosted Container Security	Alpine Linux 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 Vulnerabilities	Nessus	Windows	high
103985	Wireshark 2.2.x < 2.2.10 Multiple Vulnerabilities	Nessus	Windows	high
103983	Wireshark 2.4.x < 2.4.2 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	high
103982	Wireshark 2.2.x < 2.2.10 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	high

Detections

Analytics

CVE-2017-15193

high

Tenable Plugins

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high