In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SIGCOMP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-sigcomp.c by correcting a memory-size check.
| Vulnerable Product | Search on Vulmon | Subscribe to Product |
|---|---|---|
wireshark wireshark 2.0.0 |
||
wireshark wireshark 2.0.4 |
||
wireshark wireshark 2.2.0 |
||
wireshark wireshark 2.0.9 |
||
wireshark wireshark 2.2.2 |
||
wireshark wireshark 2.0.1 |
||
wireshark wireshark 2.2.1 |
||
wireshark wireshark 2.2.4 |
||
wireshark wireshark 2.0.11 |
||
wireshark wireshark 2.0.7 |
||
wireshark wireshark 2.0.2 |
||
wireshark wireshark 2.0.8 |
||
wireshark wireshark 2.0.3 |
||
wireshark wireshark 2.2.5 |
||
wireshark wireshark 2.0.6 |
||
wireshark wireshark 2.0.10 |
||
wireshark wireshark 2.2.3 |
||
wireshark wireshark 2.0.5 |
Vulmon