First published: Tue Jul 18 2017(Updated: )
In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the WBXML dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wbxml.c by adding validation of the relationships between indexes and lengths. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-7702.
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.0.10 | |
Wireshark Wireshark | =2.0.11 | |
Wireshark Wireshark | =2.0.12 | |
Wireshark Wireshark | =2.0.13 | |
Wireshark Wireshark | =2.2.0 | |
Wireshark Wireshark | =2.2.1 | |
Wireshark Wireshark | =2.2.2 | |
Wireshark Wireshark | =2.2.3 | |
Wireshark Wireshark | =2.2.4 | |
Wireshark Wireshark | =2.2.5 | |
Wireshark Wireshark | =2.2.6 | |
Wireshark Wireshark | =2.2.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.