Page 6 of 55 results (0.014 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 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. En Wireshark 2.2.0 a 2.2.5 y 2.0.0 a 2.0.11, el disector PacketBB podría caer, desencadenado por un paquete de inyección o un archivo de captura mal formado. Esto se trató en epan/dissectors/packet-packetbb.c restringiendo las adiciones al árbol de protocolo. • http://www.securityfocus.com/bid/97638 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13559 https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=5cfd52d6629cf8a7ab67c6bacd3431a964f43584 https://lists.debian.org/debian-lts-announce/2019/01/msg00010.html https://www.wireshark.org/security/wnpa-sec-2017-18.html • CWE-20: Improper Input Validation •

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.8EPSS: 0%CPEs: 18EXPL: 0

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. En Wireshark 2.2.0 a 2.2.5 y 2.0.0 a 2.0.11, el disector SIGCOMP 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-sigcomp.c mediante la corrección de una comprobación del tamaño de la memoria. • http://www.securityfocus.com/bid/97627 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13578 https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=acd8e1a9b17ad274bea1e01e10e4481508a1cbf0 https://www.wireshark.org/security/wnpa-sec-2017-20.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') •

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 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. En Wireshark 2.2.0 a 2.2.5 y 2.0.0 a 2.0.11, el disector WSP 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-wsp.c añadiendo un control de longitud. • http://www.securityfocus.com/bid/97628 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13581 https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=f55cbcde2c8f74b652add4450b0592082eb6acff https://www.wireshark.org/security/wnpa-sec-2017-21.html • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •