rpm package
suse/wireshark&distro=SUSE Linux Enterprise Server for Raspberry Pi 12 SP2
pkg:rpm/suse/wireshark&distro=SUSE%20Linux%20Enterprise%20Server%20for%20Raspberry%20Pi%2012%20SP2
Vulnerabilities (80)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2017-11407 | Hig | 7.5 | < 2.2.8-48.6.1 | 2.2.8-48.6.1 | Jul 18, 2017 | In Wireshark 2.2.0 to 2.2.7 and 2.0.0 to 2.0.13, the MQ dissector could crash. This was addressed in epan/dissectors/packet-mq.c by validating the fragment length before a reassembly attempt. | |
| CVE-2017-11406 | Hig | 7.5 | < 2.2.8-48.6.1 | 2.2.8-48.6.1 | Jul 18, 2017 | In Wireshark 2.2.0 to 2.2.7 and 2.0.0 to 2.0.13, the DOCSIS dissector could go into an infinite loop. This was addressed in plugins/docsis/packet-docsis.c by rejecting invalid Frame Control parameter values. | |
| CVE-2017-9766 | Hig | 7.5 | < 2.2.9-48.9.2 | 2.2.9-48.9.2 | Jun 21, 2017 | In Wireshark 2.2.7, PROFINET IO data with a high recursion depth allows remote attackers to cause a denial of service (stack exhaustion) in the dissect_IODWriteReq function in plugins/profinet/packet-dcerpc-pn-io.c. | |
| CVE-2017-9617 | Med | 5.5 | < 2.2.9-48.9.2 | 2.2.9-48.9.2 | Jun 14, 2017 | In Wireshark 2.2.7, deeply nested DAAP data may cause stack exhaustion (uncontrolled recursion) in the dissect_daap_one_tag function in epan/dissectors/packet-daap.c in the DAAP dissector. | |
| CVE-2017-9354 | Hig | 7.5 | < 2.2.7-47.1 | 2.2.7-47.1 | Jun 2, 2017 | In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the RGMP dissector could crash. This was addressed in epan/dissectors/packet-rgmp.c by validating an IPv4 address. | |
| CVE-2017-9353 | Hig | 7.5 | < 2.2.7-47.1 | 2.2.7-47.1 | Jun 2, 2017 | In Wireshark 2.2.0 to 2.2.6, the IPv6 dissector could crash. This was addressed in epan/dissectors/packet-ipv6.c by validating an IPv6 address. | |
| CVE-2017-9352 | Hig | 7.5 | < 2.2.7-47.1 | 2.2.7-47.1 | Jun 2, 2017 | In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bazaar dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-bzr.c by ensuring that backwards parsing cannot occur. | |
| CVE-2017-9351 | Hig | 7.5 | < 2.2.7-47.1 | 2.2.7-47.1 | Jun 2, 2017 | In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DHCP dissector could read past the end of a buffer. This was addressed in epan/dissectors/packet-bootp.c by extracting the Vendor Class Identifier more carefully. | |
| CVE-2017-9350 | Hig | 7.5 | < 2.2.7-47.1 | 2.2.7-47.1 | Jun 2, 2017 | 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-9349 | Hig | 7.5 | < 2.2.7-47.1 | 2.2.7-47.1 | Jun 2, 2017 | In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DICOM dissector has an infinite loop. This was addressed in epan/dissectors/packet-dcm.c by validating a length value. | |
| CVE-2017-9348 | Hig | 7.5 | < 2.2.7-47.1 | 2.2.7-47.1 | Jun 2, 2017 | In Wireshark 2.2.0 to 2.2.6, the DOF dissector could read past the end of a buffer. This was addressed in epan/dissectors/packet-dof.c by validating a size value. | |
| CVE-2017-9347 | Hig | 7.5 | < 2.2.7-47.1 | 2.2.7-47.1 | Jun 2, 2017 | In Wireshark 2.2.0 to 2.2.6, the ROS dissector could crash with a NULL pointer dereference. This was addressed in epan/dissectors/asn1/ros/packet-ros-template.c by validating an OID. | |
| CVE-2017-9346 | Hig | 7.5 | < 2.2.7-47.1 | 2.2.7-47.1 | Jun 2, 2017 | In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the SoulSeek dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-slsk.c by making loop bounds more explicit. | |
| CVE-2017-9345 | Hig | 7.5 | < 2.2.7-47.1 | 2.2.7-47.1 | Jun 2, 2017 | In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DNS dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-dns.c by trying to detect self-referencing pointers. | |
| CVE-2017-9344 | Hig | 7.5 | < 2.2.7-47.1 | 2.2.7-47.1 | Jun 2, 2017 | In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bluetooth L2CAP dissector could divide by zero. This was addressed in epan/dissectors/packet-btl2cap.c by validating an interval value. | |
| CVE-2017-9343 | Hig | 7.5 | < 2.2.7-47.1 | 2.2.7-47.1 | Jun 2, 2017 | In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the MSNIP dissector misuses a NULL pointer. This was addressed in epan/dissectors/packet-msnip.c by validating an IPv4 address. | |
| CVE-2017-7748 | Hig | 7.5 | < 2.2.6-44.3 | 2.2.6-44.3 | Apr 12, 2017 | In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WSP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wsp.c by adding a length check. | |
| CVE-2017-7747 | Hig | 7.5 | < 2.2.6-44.3 | 2.2.6-44.3 | Apr 12, 2017 | In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the PacketBB dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-packetbb.c by restricting additions to the protocol tree. | |
| CVE-2017-7746 | Hig | 7.5 | < 2.2.6-44.3 | 2.2.6-44.3 | Apr 12, 2017 | In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length. | |
| CVE-2017-7745 | Hig | 7.5 | < 2.2.6-44.3 | 2.2.6-44.3 | Apr 12, 2017 | In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SIGCOMP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-sigcomp.c by correcting a memory-size check. |
- affected < 2.2.8-48.6.1fixed 2.2.8-48.6.1
In Wireshark 2.2.0 to 2.2.7 and 2.0.0 to 2.0.13, the MQ dissector could crash. This was addressed in epan/dissectors/packet-mq.c by validating the fragment length before a reassembly attempt.
- affected < 2.2.8-48.6.1fixed 2.2.8-48.6.1
In Wireshark 2.2.0 to 2.2.7 and 2.0.0 to 2.0.13, the DOCSIS dissector could go into an infinite loop. This was addressed in plugins/docsis/packet-docsis.c by rejecting invalid Frame Control parameter values.
- affected < 2.2.9-48.9.2fixed 2.2.9-48.9.2
In Wireshark 2.2.7, PROFINET IO data with a high recursion depth allows remote attackers to cause a denial of service (stack exhaustion) in the dissect_IODWriteReq function in plugins/profinet/packet-dcerpc-pn-io.c.
- affected < 2.2.9-48.9.2fixed 2.2.9-48.9.2
In Wireshark 2.2.7, deeply nested DAAP data may cause stack exhaustion (uncontrolled recursion) in the dissect_daap_one_tag function in epan/dissectors/packet-daap.c in the DAAP dissector.
- affected < 2.2.7-47.1fixed 2.2.7-47.1
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the RGMP dissector could crash. This was addressed in epan/dissectors/packet-rgmp.c by validating an IPv4 address.
- affected < 2.2.7-47.1fixed 2.2.7-47.1
In Wireshark 2.2.0 to 2.2.6, the IPv6 dissector could crash. This was addressed in epan/dissectors/packet-ipv6.c by validating an IPv6 address.
- affected < 2.2.7-47.1fixed 2.2.7-47.1
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bazaar dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-bzr.c by ensuring that backwards parsing cannot occur.
- affected < 2.2.7-47.1fixed 2.2.7-47.1
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DHCP dissector could read past the end of a buffer. This was addressed in epan/dissectors/packet-bootp.c by extracting the Vendor Class Identifier more carefully.
- affected < 2.2.7-47.1fixed 2.2.7-47.1
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.
- affected < 2.2.7-47.1fixed 2.2.7-47.1
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DICOM dissector has an infinite loop. This was addressed in epan/dissectors/packet-dcm.c by validating a length value.
- affected < 2.2.7-47.1fixed 2.2.7-47.1
In Wireshark 2.2.0 to 2.2.6, the DOF dissector could read past the end of a buffer. This was addressed in epan/dissectors/packet-dof.c by validating a size value.
- affected < 2.2.7-47.1fixed 2.2.7-47.1
In Wireshark 2.2.0 to 2.2.6, the ROS dissector could crash with a NULL pointer dereference. This was addressed in epan/dissectors/asn1/ros/packet-ros-template.c by validating an OID.
- affected < 2.2.7-47.1fixed 2.2.7-47.1
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the SoulSeek dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-slsk.c by making loop bounds more explicit.
- affected < 2.2.7-47.1fixed 2.2.7-47.1
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DNS dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-dns.c by trying to detect self-referencing pointers.
- affected < 2.2.7-47.1fixed 2.2.7-47.1
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bluetooth L2CAP dissector could divide by zero. This was addressed in epan/dissectors/packet-btl2cap.c by validating an interval value.
- affected < 2.2.7-47.1fixed 2.2.7-47.1
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the MSNIP dissector misuses a NULL pointer. This was addressed in epan/dissectors/packet-msnip.c by validating an IPv4 address.
- affected < 2.2.6-44.3fixed 2.2.6-44.3
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WSP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wsp.c by adding a length check.
- affected < 2.2.6-44.3fixed 2.2.6-44.3
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the PacketBB dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-packetbb.c by restricting additions to the protocol tree.
- affected < 2.2.6-44.3fixed 2.2.6-44.3
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length.
- affected < 2.2.6-44.3fixed 2.2.6-44.3
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SIGCOMP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-sigcomp.c by correcting a memory-size check.
Page 3 of 4