Page 20 of 533 results (0.004 seconds)

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

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. En Wireshark 2.2.0 a 2.2.5 y 2.0.0 a 2.0.11, el disector SLSK podría entrar en un bucle infinito, desencadenado por un paquete de inyección o un archivo de captura mal formado. Esto se trató en epan/dissectors/packet-slsk.c añadiendo controles para la longitud restante. • http://www.securityfocus.com/bid/97635 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13576 https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=58e69cc769dea24b721abd8a29f9eedc11024b7e https://lists.debian.org/debian-lts-announce/2019/01/msg00010.html https://www.wireshark.org/security/wnpa-sec-2017-19.html • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •

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

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the NetScaler file parser could go into an infinite loop, triggered by a malformed capture file. This was addressed in wiretap/netscaler.c by ensuring a nonzero record size. En Wireshark 2.2.0 a 2.2.5 y 2.0.0 a 2.0.11, el analizador de archivos NetScaler podría entrar en un bucle infinito, desencadenado por un archivo de captura malformado. Esto se trató en wiretap/netscaler.c asegurando un tamaño de registro distinto a cero. • http://www.securityfocus.com/bid/97631 http://www.securitytracker.com/id/1038262 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13478 https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=8fc0af859de4993951a915ad735be350221f3f53 https://lists.debian.org/debian-lts-announce/2019/01/msg00010.html https://security.gentoo.org/glsa/201706-12 https://www.wireshark.org/security/wnpa-sec-2017-14.html • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •

CVSS: 7.8EPSS: 0%CPEs: 18EXPL: 0

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the BGP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-bgp.c by using a different integer data type. En Wireshark 2.2.0 a 2.2.5 y 2.0.0 a 2.0.11, el disector BGP podría entrar en un bucle infinito, desencadenado por un paquete de inyección o un archivo de captura mal formado. Esto se trató en epan/dissectors/packet-bgp.c mediante el uso de un tipo de datos íntegros diferente. • http://www.securityfocus.com/bid/97632 http://www.securitytracker.com/id/1038262 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13557 https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=fa31f69b407436d0946f84baa0acdcc50962bf7a https://security.gentoo.org/glsa/201706-12 https://www.wireshark.org/security/wnpa-sec-2017-16.html • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •

CVSS: 7.8EPSS: 0%CPEs: 18EXPL: 0

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WBXML dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wbxml.c by adding length validation. En Wireshark 2.2.0 a 2.2.5 y 2.0.0 a 2.0.11, el disector WBXML podría entrar en un bucle infinito, desencadenado por un paquete de inyección o un archivo de captura mal formado. Esto se trató en epan/dissectors/packet-wbxml.c agregando validación de longitud. • http://www.securityfocus.com/bid/97633 http://www.securitytracker.com/id/1038262 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13477 https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=2f322f66cbcca2fefdaa630494f9d6c97eb659b7 https://security.gentoo.org/glsa/201706-12 https://www.wireshark.org/security/wnpa-sec-2017-13.html • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •

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

In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the IMAP dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-imap.c by calculating a line's end correctly. En Wireshark 2.2.0 a 2.2.5 y 2.0.0 a 2.0.11, el disector IMAP podría caer, desencadenado por un paquete de inyección o un archivo de captura mal formado. Esto se trató en epan/dissectors/packet-imap.c calculando el final de una línea correctamente. • http://www.securityfocus.com/bid/97636 http://www.securitytracker.com/id/1038262 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13466 https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=671e32820ab29d41d712cc8a472eab9b672684d9 https://lists.debian.org/debian-lts-announce/2019/01/msg00010.html https://security.gentoo.org/glsa/201706-12 https://www.wireshark.org/security/wnpa-sec-2017-12.html • CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') •