The Quarterly Threat Landscape Report is out. See what attackers are targeting now.Read report
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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade wireshark | Jul 30, 2024 | Apr 12, 2017 |
| Oracle Solaris | — | Upgrade diagnostic/wireshark/tshark to version 2.2.6-0.175.3.21.0.4.0 on Solaris 11.3Upgrade diagnostic/wireshark/wireshark-common to version 2.2.6-0.175.3.21.0.4.0 on Solaris 11.3Upgrade diagnostic/wireshark to version 2.2.6-0.175.3.21.0.4.0 on Solaris 11.3 | Jun 27, 2017 | Apr 12, 2017 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Apr 12, 2017 |
| Suse | — | Upgrade wireshark-develUpgrade libwireshark9Upgrade libwireshark13Upgrade libwsutil8Upgrade libwireshark8Upgrade libwsutil11Upgrade wiresharkUpgrade libwiretap10Upgrade wireshark-gtkUpgrade wireshark-ui-qtUpgrade libwscodecs1Upgrade libwiretap6Upgrade libwsutil7Upgrade libwiretap7 | Apr 21, 2017 | Apr 12, 2017 |
| Ubuntu | — | Upgrade wireshark | Nov 19, 2024 | Apr 12, 2017 |
| Wireshark | — | Upgrade to Wireshark version 2.0.12Upgrade to Wireshark version 2.2.6 | Apr 25, 2018 | Apr 12, 2017 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub