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.

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.

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.0.0 to 2.0.13, the GPRS LLC dissector could go into a large loop. This was addressed in     epan/dissectors/packet-gprs-llc.c by using a different integer data type. (CVE-2017-11409)

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

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.

ID	Name	Product	Family	Published	Updated	Severity
311404	Wireshark 2.0.x < 2.0.14 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	5/1/2026	5/1/2026	high
121193	Debian DLA-1634-1 : wireshark security update	Nessus	Debian Local Security Checks	1/16/2019	6/26/2024	high
220443	Linux Distros Unpatched Vulnerability : CVE-2017-11409	Nessus	Misc.	3/4/2025	9/15/2025	high
311403	Wireshark 2.0.x < 2.0.14 Multiple Vulnerabilities	Nessus	Windows	5/1/2026	5/1/2026	high

Detections

Analytics

Plugins Search

high

high

high

high