CVE-2017-5596: Integer Overflow
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.
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2017-5596?
CVE-2017-5596 is categorized as a medium severity vulnerability due to its potential to cause denial of service through an infinite loop.
How do I fix CVE-2017-5596?
To fix CVE-2017-5596, upgrade Wireshark to version 2.2.4 or later, or to version 2.0.10 or later.
What versions of Wireshark are affected by CVE-2017-5596?
CVE-2017-5596 affects Wireshark versions 2.0.0 to 2.0.9 and 2.2.0 to 2.2.3.
What is the cause of the CVE-2017-5596 vulnerability?
The CVE-2017-5596 vulnerability is caused by the ASTERIX dissector entering an infinite loop due to a data type issue that allows integer overflow.
Can CVE-2017-5596 be exploited remotely?
Yes, CVE-2017-5596 can be exploited remotely through packet injection or by using a malformed capture file.