Vulnerability & Exploit Database

Displaying all 5 entries

Results for: CVE-2017-5596 Back to search

Wireshark : CVE-2017-5596 : ASTERIX infinite loop Vulnerability

  • Severity: 5
  • Published: January 25, 2017

In Wireshark 2.2.0 to 2.2.3 and 2.0.0 to 2.0.9, the ASTERIX dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-asterix.c by changing a data type to avoid an integer overflow.

SUSE: CVE-2017-5596: SUSE Linux Security Advisory Vulnerability

  • Severity: 5
  • Published: January 25, 2017

In Wireshark 2.2.0 to 2.2.3 and 2.0.0 to 2.0.9, the ASTERIX dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-asterix.c by changing a data type to avoid an integer overflow.

Oracle Solaris 11: CVE-2017-5596: Vulnerability in Wireshark Vulnerability

  • Severity: 5
  • Published: January 25, 2017

In Wireshark 2.2.0 to 2.2.3 and 2.0.0 to 2.0.9, the ASTERIX dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-asterix.c by changing a data type to avoid an integer overflow.

Debian: CVE-2017-5596: wireshark -- security update Vulnerability

  • Severity: 5
  • Published: January 25, 2017

In Wireshark 2.2.0 to 2.2.3 and 2.0.0 to 2.0.9, the ASTERIX dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-asterix.c by changing a data type to avoid an integer overflow.

Alpine Linux: CVE-2017-5596: wireshark Multiple issues Vulnerability

  • Severity: 5
  • Published: January 25, 2017

In Wireshark 2.2.0 to 2.2.3 and 2.0.0 to 2.0.9, the ASTERIX dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-asterix.c by changing a data type to avoid an integer overflow.