First published: Wed Jan 25 2017(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Wireshark Wireshark | =2.0.0 | |
Wireshark Wireshark | =2.0.1 | |
Wireshark Wireshark | =2.0.2 | |
Wireshark Wireshark | =2.0.3 | |
Wireshark Wireshark | =2.0.4 | |
Wireshark Wireshark | =2.0.5 | |
Wireshark Wireshark | =2.0.6 | |
Wireshark Wireshark | =2.0.7 | |
Wireshark Wireshark | =2.0.8 | |
Wireshark Wireshark | =2.0.9 | |
Wireshark Wireshark | =2.2.0 | |
Wireshark Wireshark | =2.2.1 | |
Wireshark Wireshark | =2.2.2 | |
Wireshark Wireshark | =2.2.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-5596 is categorized as a medium severity vulnerability due to its potential to cause denial of service through an infinite loop.
To fix CVE-2017-5596, upgrade Wireshark to version 2.2.4 or later, or to version 2.0.10 or later.
CVE-2017-5596 affects Wireshark versions 2.0.0 to 2.0.9 and 2.2.0 to 2.2.3.
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.
Yes, CVE-2017-5596 can be exploited remotely through packet injection or by using a malformed capture file.