Summary
This update for wireshark fixes the following issues:
Security issue fixed (bsc#1082692):
- CVE-2018-7335: The IEEE 802.11 dissector could crash (wnpa-sec-2018-05)
- CVE-2018-7321: thrift long dissector loop (dissect_thrift_map)
- CVE-2018-7322: DICOM: inifinite loop (dissect_dcm_tag)
- CVE-2018-7323: WCCP: very long loop (dissect_wccp2_alternate_mask_value_set_element)
- CVE-2018-7324: SCCP: infinite loop (dissect_sccp_optional_parameters)
- CVE-2018-7325: RPKI-Router Protocol: infinite loop (dissect_rpkirtr_pdu)
- CVE-2018-7326: LLTD: infinite loop (dissect_lltd_tlv)
- CVE-2018-7327: openflow_v6: infinite loop (dissect_openflow_bundle_control_v6)
- CVE-2018-7328: USB-DARWIN: long loop (dissect_darwin_usb_iso_transfer)
- CVE-2018-7329: S7COMM: infinite loop (s7comm_decode_ud_cpu_alarm_main)
- CVE-2018-7330: thread_meshcop: infinite loop (get_chancount)
- CVE-2018-7331: GTP: infinite loop (dissect_gprscdr_GGSNPDPRecord, dissect_ber_set)
- CVE-2018-7332: RELOAD: infinite loop (dissect_statans)
- CVE-2018-7333: RPCoRDMA: infinite loop in get_write_list_chunk_count
- CVE-2018-7421: Multiple dissectors could go into large infinite loops (wnpa-sec-2018-06)
- CVE-2018-7334: The UMTS MAC dissector could crash (wnpa-sec-2018-07)
- CVE-2018-7337: The DOCSIS dissector could crash (wnpa-sec-2018-08)
- CVE-2018-7336: The FCP dissector could crash (wnpa-sec-2018-09)
- CVE-2018-7320: The SIGCOMP dissector could crash (wnpa-sec-2018-10)
- CVE-2018-7420: The pcapng file parser could crash (wnpa-sec-2018-11)
- CVE-2018-7417: The IPMI dissector could crash (wnpa-sec-2018-12)
- CVE-2018-7418: The SIGCOMP dissector could crash (wnpa-sec-2018-13)
- CVE-2018-7419: The NBAP disssector could crash (wnpa-sec-2018-14)
- CVE-2017-17997: Misuse of NULL pointer in MRDISC dissector (bsc#1077080).
Fixed packages 9
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLES 12 SP2 Linux Enterprise Desktop 12 SP2 | wireshark | 2.2.13-48.21.1 |
| SUSE · SLES 12 SP3 Linux Enterprise Desktop 12 SP3 | wireshark | 2.2.13-48.21.1 |
| SUSE · SLES 12 SP2 Linux Enterprise Server 12 SP2 | wireshark | 2.2.13-48.21.1 |
| SUSE · SLES 12 SP3 Linux Enterprise Server 12 SP3 | wireshark | 2.2.13-48.21.1 |
| SUSE · SLES 12 SP2 Linux Enterprise Server for Raspberry Pi 12 SP2 | wireshark | 2.2.13-48.21.1 |
| SUSE · SLES for SAP 12 SP2 Linux Enterprise Server for SAP Applications 12 SP2 | wireshark | 2.2.13-48.21.1 |
| SUSE · SLES for SAP 12 SP3 Linux Enterprise Server for SAP Applications 12 SP3 | wireshark | 2.2.13-48.21.1 |
| SUSE · SLES 12 SP2 Linux Enterprise Software Development Kit 12 SP2 | wireshark | 2.2.13-48.21.1 |
| SUSE · SLES 12 SP3 Linux Enterprise Software Development Kit 12 SP3 | wireshark | 2.2.13-48.21.1 |
Vulnerabilities 24
-
Unscored —
In Wireshark before 2.2.12, the MRDISC dissector misuses a NULL pointer and crashes. This was addressed in epan/dissect…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, the SIGCOMP protocol dissector could crash. This was addressed in epan…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-thrift.c had a large loop that was addressed by…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-dcm.c had an infinite loop that was addressed b…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-wccp.c had a large loop that was addressed by e…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-sccp.c had an infinite loop that was addressed …
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-rpki-rtr.c had an infinite loop that was addres…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-lltd.c had an infinite loop that was addressed …
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-openflow_v6.c had an infinite loop that was add…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-usb.c had an infinite loop that was addressed b…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-s7comm.c had an infinite loop that was addresse…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-thread.c had an infinite loop that was addresse…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-ber.c had an infinite loop that was addressed b…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-reload.c had an infinite loop that was addresse…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-rpcrdma.c had an infinite loop that was address…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, the UMTS MAC dissector could crash. This was addressed in epan/dissect…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, the IEEE 802.11 dissector could crash. This was addressed in epan/cryp…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, the FCP protocol dissector could crash. This was addressed in epan/dis…
-
Unscored —
In Wireshark 2.4.0 to 2.4.4, the DOCSIS protocol dissector could crash. This was addressed in plugins/docsis/packet-doc…
-
Unscored —
In Wireshark 2.2.0 to 2.2.12 and 2.4.0 to 2.4.4, the IPMI dissector could crash. This was addressed in epan/dissectors/…
-
Unscored —
In Wireshark 2.2.0 to 2.2.12 and 2.4.0 to 2.4.4, the SIGCOMP dissector could crash. This was addressed in epan/dissecto…
-
Unscored —
In Wireshark 2.2.0 to 2.2.12 and 2.4.0 to 2.4.4, the NBAP dissector could crash. This was addressed in epan/dissectors/…
-
Unscored —
In Wireshark 2.2.0 to 2.2.12 and 2.4.0 to 2.4.4, the pcapng file parser could crash. This was addressed in wiretap/pcap…
-
Unscored —
In Wireshark 2.2.0 to 2.2.12 and 2.4.0 to 2.4.4, the DMP dissector could go into an infinite loop. This was addressed i…
References
-
report
https://bugzilla.suse.com/1077080
-
report
https://bugzilla.suse.com/1082692
-
web
https://www.suse.com/security/cve/CVE-2017-17997
-
web
https://www.suse.com/security/cve/CVE-2018-7320
-
web
https://www.suse.com/security/cve/CVE-2018-7321
-
web
https://www.suse.com/security/cve/CVE-2018-7322
-
web
https://www.suse.com/security/cve/CVE-2018-7323
-
web
https://www.suse.com/security/cve/CVE-2018-7324
-
web
https://www.suse.com/security/cve/CVE-2018-7325
-
web
https://www.suse.com/security/cve/CVE-2018-7326
-
web
https://www.suse.com/security/cve/CVE-2018-7327
-
web
https://www.suse.com/security/cve/CVE-2018-7328
-
web
https://www.suse.com/security/cve/CVE-2018-7329
-
web
https://www.suse.com/security/cve/CVE-2018-7330
-
web
https://www.suse.com/security/cve/CVE-2018-7331
-
web
https://www.suse.com/security/cve/CVE-2018-7332
-
web
https://www.suse.com/security/cve/CVE-2018-7333
-
web
https://www.suse.com/security/cve/CVE-2018-7334
-
web
https://www.suse.com/security/cve/CVE-2018-7335
-
web
https://www.suse.com/security/cve/CVE-2018-7336
-
web
https://www.suse.com/security/cve/CVE-2018-7337
-
web
https://www.suse.com/security/cve/CVE-2018-7417
-
web
https://www.suse.com/security/cve/CVE-2018-7418
-
web
https://www.suse.com/security/cve/CVE-2018-7419
-
web
https://www.suse.com/security/cve/CVE-2018-7420
-
web
https://www.suse.com/security/cve/CVE-2018-7421