This update for wireshark to version 2.4.9 fixes the following issues :

Wireshark was updated to 2.4.9 (bsc#1094301, bsc#1106514).

Security issues fixed :

CVE-2018-16058: Bluetooth AVDTP dissector crash (wnpa-sec-2018-44)

CVE-2018-16056: Bluetooth Attribute Protocol dissector crash (wnpa-sec-2018-45)

CVE-2018-16057: Radiotap dissector crash (wnpa-sec-2018-46)

CVE-2018-11355: Fix RTCP dissector crash (bsc#1094301).

CVE-2018-14370: IEEE 802.11 dissector crash (wnpa-sec-2018-43, bsc#1101802)

CVE-2018-14368: Bazaar dissector infinite loop (wnpa-sec-2018-40, bsc#1101794)

CVE-2018-11362: Fix LDSS dissector crash (bsc#1094301).

CVE-2018-11361: Fix IEEE 802.11 dissector crash (bsc#1094301).

CVE-2018-11360: Fix GSM A DTAP dissector crash (bsc#1094301).

CVE-2018-14342: BGP dissector large loop (wnpa-sec-2018-34, bsc#1101777)

CVE-2018-14343: ASN.1 BER dissector crash (wnpa-sec-2018-37, bsc#1101786)

CVE-2018-14340: Multiple dissectors could crash (wnpa-sec-2018-36, bsc#1101804)

CVE-2018-14341: DICOM dissector crash (wnpa-sec-2018-39, bsc#1101776)

CVE-2018-11358: Fix Q.931 dissector crash (bsc#1094301).

CVE-2018-14344: ISMP dissector crash (wnpa-sec-2018-35, bsc#1101788)

CVE-2018-11359: Fix multiple dissectors crashs (bsc#1094301).

CVE-2018-11356: Fix DNS dissector crash (bsc#1094301).

CVE-2018-14339: MMSE dissector infinite loop (wnpa-sec-2018-38, bsc#1101810)

CVE-2018-11357: Fix multiple dissectors that could consume excessive memory (bsc#1094301).

CVE-2018-14367: CoAP dissector crash (wnpa-sec-2018-42, bsc#1101791)

CVE-2018-11354: Fix IEEE 1905.1a dissector crash (bsc#1094301).

CVE-2018-14369: HTTP2 dissector crash (wnpa-sec-2018-41, bsc#1101800)

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

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.

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

  - In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LDSS dissector could crash. This was     addressed in epan/dissectors/packet-ldss.c by avoiding a buffer over-read upon encountering a missing '\0'     character. (CVE-2018-11362)

  - In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed     in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
    (CVE-2018-11356)

  - In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could     consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
    (CVE-2018-11357)

  - In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the Q.931 dissector could crash. This was     addressed in epan/dissectors/packet-q931.c by avoiding a use-after-free after a malformed packet prevented     certain cleanup. (CVE-2018-11358)

  - In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the RRC dissector and other dissectors could     crash. This was addressed in epan/proto.c by avoiding a NULL pointer dereference. (CVE-2018-11359)

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

  - In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LDSS dissector could crash. This was     addressed in epan/dissectors/packet-ldss.c by avoiding a buffer over-read upon encountering a missing '\0'     character. (CVE-2018-11362)

  - In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-     ieee1905.c by making a certain correction to string handling. (CVE-2018-11354)

  - In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by     avoiding a buffer overflow for packet status chunks. (CVE-2018-11355)

  - In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed     in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
    (CVE-2018-11356)

  - In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could     consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
    (CVE-2018-11357)

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

  - In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LDSS dissector could crash. This was     addressed in epan/dissectors/packet-ldss.c by avoiding a buffer over-read upon encountering a missing '\0'     character. (CVE-2018-11362)

  - In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-     ieee1905.c by making a certain correction to string handling. (CVE-2018-11354)

  - In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by     avoiding a buffer overflow for packet status chunks. (CVE-2018-11355)

  - In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed     in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
    (CVE-2018-11356)

  - In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could     consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
    (CVE-2018-11357)

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
117821	SUSE SLED12 / SLES12 Security Update : wireshark (SUSE-SU-2018:2891-1)	Nessus	SuSE Local Security Checks	9/28/2018	8/1/2024	high
311464	Wireshark 2.2.x < 2.2.15 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	5/1/2026	10/5/2026	high
110268	Wireshark 2.6.x < 2.6.1 Multiple Vulnerabilities (macOS)	Nessus	MacOS X Local Security Checks	5/31/2018	10/15/2026	high
110269	Wireshark 2.6.x < 2.6.1 Multiple Vulnerabilities	Nessus	Windows	5/31/2018	10/15/2026	high

Detections

Analytics

Plugins Search

high

high

high

high