5959 matches found
CVE-2017-9344
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...
DEBIAN-CVE-2017-9349
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...
ALPINE-CVE-2017-9344
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...
DEBIAN-CVE-2017-9352
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-9354
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-9349
CVE-2017-9349 affects the DICOM dissector in Wireshark from 2.0.0–2.0.12 and 2.2.0–2.2.6, where an infinite loop could be triggered. The root cause is a length value not being validated, leading to a looping condition. The issue was fixed upstream by validating the length in epan/dissectors/packe...
CVE-2017-9344
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-9349
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-9353
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-9345
CVE-2017-9345 affects Wireshark 2.2.0–2.2.6 and 2.0.0–2.0.12, where the DNS dissector could enter an infinite loop. The root cause is a flaw in DNS dissector flow that could loop on certain inputs; upstream fix involved detecting self-referencing pointers in epan/dissectors/packet-dns.c. The impa...
CVE-2017-9345
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-9353
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-9354
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-9352
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-9348
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-9346
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-9351
Wireshark DHCP dissector (versions 2.2.0–2.2.6 and 2.0.0–2.0.12) could read past the end of a buffer due to insufficient bounds checking when extracting the Vendor Class Identifier. Root cause: a bounds issue in epan/dissectors/packet-bootp.c. Fix implemented in the code path handling Vendor Clas...
CVE-2017-9353
The CVE-2017-9353 entry refers to Wireshark 2.2.0–2.2.6 where the IPv6 dissector could crash. The root cause, per the description, is an insufficient validation of IPv6 addresses in epan/dissectors/packet-ipv6.c, which could trigger a crash (reported as a potential denial of service in some advis...