In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the WBXML dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wbxml.c by adding validation of the relationships between indexes and lengths. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-7702.

The version of Wireshark installed on the remote macOS / Mac OS X host is prior to 2.0.14. It is, therefore, affected by multiple vulnerabilities as referenced in the wireshark-2.0.14 advisory.

  - In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the openSAFETY dissector could crash or exhaust     system memory. This was addressed in epan/dissectors/packet-opensafety.c by adding length validation.
    NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-9350. (CVE-2017-11411)

  - In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the openSAFETY dissector could crash or exhaust system     memory. This was addressed in epan/dissectors/packet-opensafety.c by checking for a negative length.
    (CVE-2017-9350)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding length validation. (CVE-2017-7702)

  - In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding validation of the relationships between indexes and lengths. NOTE: this vulnerability     exists because of an incomplete fix for CVE-2017-7702. (CVE-2017-11410)

  - In Wireshark 2.2.0 to 2.2.7 and 2.0.0 to 2.0.13, the AMQP dissector could crash. This was addressed in     epan/dissectors/packet-amqp.c by checking for successful list dissection. (CVE-2017-11408)

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

  - In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the openSAFETY dissector could crash or exhaust     system memory. This was addressed in epan/dissectors/packet-opensafety.c by adding length validation.
    NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-9350. (CVE-2017-11411)

  - In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the openSAFETY dissector could crash or exhaust system     memory. This was addressed in epan/dissectors/packet-opensafety.c by checking for a negative length.
    (CVE-2017-9350)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding length validation. (CVE-2017-7702)

  - In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding validation of the relationships between indexes and lengths. NOTE: this vulnerability     exists because of an incomplete fix for CVE-2017-7702. (CVE-2017-11410)

  - In Wireshark 2.2.0 to 2.2.7 and 2.0.0 to 2.0.13, the AMQP dissector could crash. This was addressed in     epan/dissectors/packet-amqp.c by checking for successful list dissection. (CVE-2017-11408)

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

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite     loop, triggered by packet injection or a malformed capture file. This was addressed in     epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset.
    (CVE-2017-7705)

  - In Wireshark 2.2.0 to 2.2.4 and 2.0.0 to 2.0.10, there is an RTMPT dissector infinite loop, triggered by     packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rtmpt.c by     properly incrementing a certain sequence value. (CVE-2017-6472)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the IMAP dissector could crash, triggered by packet     injection or a malformed capture file. This was addressed in epan/dissectors/packet-imap.c by calculating     a line's end correctly. (CVE-2017-7703)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding length validation. (CVE-2017-7702)

  - In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding validation of the relationships between indexes and lengths. NOTE: this vulnerability     exists because of an incomplete fix for CVE-2017-7702. (CVE-2017-11410)

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

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite     loop, triggered by packet injection or a malformed capture file. This was addressed in     epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset.
    (CVE-2017-7705)

  - In Wireshark 2.2.0 to 2.2.4 and 2.0.0 to 2.0.10, there is an RTMPT dissector infinite loop, triggered by     packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rtmpt.c by     properly incrementing a certain sequence value. (CVE-2017-6472)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the IMAP dissector could crash, triggered by packet     injection or a malformed capture file. This was addressed in epan/dissectors/packet-imap.c by calculating     a line's end correctly. (CVE-2017-7703)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding length validation. (CVE-2017-7702)

  - In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding validation of the relationships between indexes and lengths. NOTE: this vulnerability     exists because of an incomplete fix for CVE-2017-7702. (CVE-2017-11410)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

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

  - In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding validation of the relationships between indexes and lengths. NOTE: this vulnerability     exists because of an incomplete fix for CVE-2017-7702. (CVE-2017-11410)

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

This wireshark update to version 2.2.8 fixes the following issues:
Security issues fixed :

  - CVE-2017-11411: The openSAFETY dissectorcould crash or     exhaust system memory because of missing length     validation. (bsc#1049621)

  - CVE-2017-11410: The WBXML dissector could go into an     infinite loop. (bsc#1049255)

  - CVE-2017-11408: The AMQP dissector could crash.
    (bsc#1049255)

  - CVE-2017-11407: The MQ dissector could crash.
    (bsc#1049255)

  - CVE-2017-11406: The DOCSIS dissector could go into an     infinite loop. (bsc#1049255)

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 to Wireshark 2.2.8 fixes some minor vulnerabilities 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-7702,CVE-2017-11410: WBMXL dissector infinite     loop (wnpa-sec-2017-13)

  - CVE-2017-9350,CVE-2017-11411: openSAFETY dissector     memory exhaustion (wnpa-sec-2017-28)

  - CVE-2017-11408: AMQP dissector crash (wnpa-sec-2017-34)

  - CVE-2017-11407: MQ dissector crash (wnpa-sec-2017-35)

  - CVE-2017-11406: DOCSIS infinite loop (wnpa-sec-2017-36)

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

  - In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the openSAFETY dissector could crash or exhaust     system memory. This was addressed in epan/dissectors/packet-opensafety.c by adding length validation.
    NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-9350. (CVE-2017-11411)

  - In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the openSAFETY dissector could crash or exhaust system     memory. This was addressed in epan/dissectors/packet-opensafety.c by checking for a negative length.
    (CVE-2017-9350)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding length validation. (CVE-2017-7702)

  - In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding validation of the relationships between indexes and lengths. NOTE: this vulnerability     exists because of an incomplete fix for CVE-2017-7702. (CVE-2017-11410)

  - In Wireshark 2.2.0 to 2.2.7 and 2.0.0 to 2.0.13, the AMQP dissector could crash. This was addressed in     epan/dissectors/packet-amqp.c by checking for successful list dissection. (CVE-2017-11408)

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

  - In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the openSAFETY dissector could crash or exhaust     system memory. This was addressed in epan/dissectors/packet-opensafety.c by adding length validation.
    NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-9350. (CVE-2017-11411)

  - In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the openSAFETY dissector could crash or exhaust system     memory. This was addressed in epan/dissectors/packet-opensafety.c by checking for a negative length.
    (CVE-2017-9350)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding length validation. (CVE-2017-7702)

  - In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding validation of the relationships between indexes and lengths. NOTE: this vulnerability     exists because of an incomplete fix for CVE-2017-7702. (CVE-2017-11410)

  - In Wireshark 2.2.0 to 2.2.7 and 2.0.0 to 2.0.13, the AMQP dissector could crash. This was addressed in     epan/dissectors/packet-amqp.c by checking for successful list dissection. (CVE-2017-11408)

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

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite     loop, triggered by packet injection or a malformed capture file. This was addressed in     epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset.
    (CVE-2017-7705)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the IMAP dissector could crash, triggered by packet     injection or a malformed capture file. This was addressed in epan/dissectors/packet-imap.c by calculating     a line's end correctly. (CVE-2017-7703)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding length validation. (CVE-2017-7702)

  - In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding validation of the relationships between indexes and lengths. NOTE: this vulnerability     exists because of an incomplete fix for CVE-2017-7702. (CVE-2017-11410)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the NetScaler file parser could go into an infinite loop,     triggered by a malformed capture file. This was addressed in wiretap/netscaler.c by ensuring a nonzero     record size. (CVE-2017-7700)

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

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite     loop, triggered by packet injection or a malformed capture file. This was addressed in     epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset.
    (CVE-2017-7705)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the IMAP dissector could crash, triggered by packet     injection or a malformed capture file. This was addressed in epan/dissectors/packet-imap.c by calculating     a line's end correctly. (CVE-2017-7703)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding length validation. (CVE-2017-7702)

  - In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the WBXML dissector could go into an infinite loop,     triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-     wbxml.c by adding validation of the relationships between indexes and lengths. NOTE: this vulnerability     exists because of an incomplete fix for CVE-2017-7702. (CVE-2017-11410)

  - In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the NetScaler file parser could go into an infinite loop,     triggered by a malformed capture file. This was addressed in wiretap/netscaler.c by ensuring a nonzero     record size. (CVE-2017-7700)

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
311404	Wireshark 2.0.x < 2.0.14 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	high
311403	Wireshark 2.0.x < 2.0.14 Multiple Vulnerabilities	Nessus	Windows	high
311400	Wireshark 2.0.x < 2.0.12 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	high
311399	Wireshark 2.0.x < 2.0.12 Multiple Vulnerabilities	Nessus	Windows	high
220412	Linux Distros Unpatched Vulnerability : CVE-2017-11410	Nessus	Misc.	high
102190	SUSE SLED12 / SLES12 Security Update : wireshark (SUSE-SU-2017:2033-1)	Nessus	SuSE Local Security Checks	high
102189	SUSE SLES11 Security Update : wireshark (SUSE-SU-2017:2032-1)	Nessus	SuSE Local Security Checks	high
101970	openSUSE Security Update : Wireshark (openSUSE-2017-840)	Nessus	SuSE Local Security Checks	high
101898	Wireshark 2.2.x < 2.2.8 Multiple Vulnerabilities	Nessus	Windows	high
101897	Wireshark 2.2.x < 2.2.8 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	high
99437	Wireshark 2.2.x < 2.2.6 Multiple Vulnerabilities	Nessus	Windows	high
99436	Wireshark 2.2.x < 2.2.6 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	high

Detections

Analytics

CVE-2017-11410

high

Tenable Plugins

high

high

high

high

high

high

high

high

high

high

high

high