Page 5 of 102 results (0.007 seconds)

CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 1

In Wireshark 2.6.0 to 2.6.4 and 2.4.0 to 2.4.10, the DCOM dissector could crash. This was addressed in epan/dissectors/packet-dcom.c by adding '\0' termination. En Wireshark 2.6.0 a 2.6.4 y 2.4.0 a 2.4.10, el disector DCOM podría cerrarse inesperadamente. Esto se trató en epan/dissectors/packet-dcom.c añadiendo la terminación "\0". • http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00027.html http://www.securityfocus.com/bid/106051 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15130 https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=c5a65115ebab55cfd5ce0a855c2256e01cab6449 https://lists.debian.org/debian-lts-announce/2019/01/msg00010.html https://www.debian.org/security/2018/dsa-4359 https://www.oracle.com/security-alerts/cpuapr2020.html https://www.wireshark.org/security/wnpa-sec-2018&# • CWE-125: Out-of-bounds Read CWE-908: Use of Uninitialized Resource •

CVSS: 7.5EPSS: 2%CPEs: 3EXPL: 2

In Wireshark 2.6.0 to 2.6.4 and 2.4.0 to 2.4.10, the IxVeriWave file parser could crash. This was addressed in wiretap/vwr.c by adjusting a buffer boundary. En Wireshark 2.6.0 a 2.6.4 y 2.4.0 a 02/04/2010, el analizador IxVeriWave de archivos podría cerrarse inesperadamente. Esto se abordó en wiretap/vwr.c ajustando un límite de búfer. Wireshark suffers from a heap out-of-bounds read in find_signature. • https://www.exploit-db.com/exploits/45951 http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00027.html http://www.securityfocus.com/bid/106051 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15279 https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=bdc33cfaecb1b4cf2c114ed9015713ddf8569a60 https://www.debian.org/security/2018/dsa-4359 https://www.oracle.com/security-alerts/cpuapr2020.html https://www.wireshark.org/security/wnpa-sec-2018-55.html • CWE-125: Out-of-bounds Read •

CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 1

In Wireshark 2.6.0 to 2.6.4 and 2.4.0 to 2.4.10, the MMSE dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-mmse.c by preventing length overflows. En Wireshark, de la versión 2.6.0 a la 2.6.4 y de la versión 2.4.0 a la 2.4.10, el disector MMSE podría entrar en un bucle infinito. Esto se trató en epan/dissectors/packet-mmse.c evitando desbordamientos de longitud. A vulnerability in MMSE dissector allows Wireshark to loop infinitely when parsing a specially crafted pcap file. • http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00027.html http://www.securityfocus.com/bid/106051 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15250 https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=3b7555d32d11862f0e500ec466ad6bfe54190076 https://lists.debian.org/debian-lts-announce/2019/01/msg00010.html https://www.debian.org/security/2018/dsa-4359 https://www.oracle.com/security-alerts/cpuapr2020.html https://www.wireshark.org/security/wnpa-sec-2018&# • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •

CVSS: 7.5EPSS: 0%CPEs: 3EXPL: 0

In Wireshark 2.6.0 to 2.6.3 and 2.4.0 to 2.4.9, the MS-WSP protocol dissector could crash. This was addressed in epan/dissectors/packet-mswsp.c by properly handling NULL return values. En Wireshark de la versión 2.6.0 a la 2.6.3 y de la versión 2.4.0 a la 2.4.9, el disector del protocolo MS-WSP podría cerrarse inesperadamente. Esto se trató en epan/dissectors/packet-mswsp.c gestionando correctamente valores NULL de retorno. • http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00027.html http://www.securityfocus.com/bid/105583 http://www.securitytracker.com/id/1041909 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15119 https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=d443be449a52f95df5754adc39e1f3472fec2f03 https://www.debian.org/security/2018/dsa-4359 https://www.oracle.com/security-alerts/cpuapr2020.html https://www.wireshark.org/security/wnpa-sec-2018-47.html • CWE-476: NULL Pointer Dereference •

CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0

In Wireshark 2.6.0 to 2.6.2, 2.4.0 to 2.4.8, and 2.2.0 to 2.2.16, the Bluetooth Attribute Protocol dissector could crash. This was addressed in epan/dissectors/packet-btatt.c by verifying that a dissector for a specific UUID exists. En Wireshark, de la versión 2.6.0 a la 2.6.2, de la versión 2.4.0 a la 2.4.8 y de la versión 2.2.0 a la 2.2.16, el disector Bluetooth Attribute Protocol podría cerrarse inesperadamente. Esto se abordó en epan/dissectors/packet-btatt.c verificando que existe un disector para un UUID concreto. • http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00027.html http://www.securityfocus.com/bid/105174 http://www.securitytracker.com/id/1041609 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14994 https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=f98fbce64cb230e94a2cafc410a3cedad657b485 https://www.debian.org/security/2018/dsa-4315 https://www.wireshark.org/security/wnpa-sec-2018-45.html •