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 DHCPv6 dissector could go into a large loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-dhcpv6.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-5597 is considered a medium severity vulnerability due to its potential to cause a denial of service.
To fix CVE-2017-5597, upgrade Wireshark to version 2.2.4 or later, or 2.0.10 or later.
CVE-2017-5597 affects Wireshark versions 2.0.0 to 2.0.9 and 2.2.0 to 2.2.3.
CVE-2017-5597 involves a potential denial of service through packet injection or malformed capture files.
CVE-2017-5597 can cause Wireshark to enter a large loop, significantly impacting system stability.