In Wireshark 2.2.0 to 2.2.7 and 2.0.0 to 2.0.13, the DOCSIS dissector could go into an infinite loop. This was addressed in plugins/docsis/packet-docsis.c by rejecting invalid Frame Control parameter values.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade wireshark | Sep 20, 2017 | Jul 18, 2017 |
| Arch Linux | — | Upgrade to the latest version of Arch Linux | Jul 11, 2025 | Jul 18, 2017 |
| Debian | — | Upgrade wireshark | Feb 20, 2019 | Jul 18, 2017 |
| Oracle Solaris | — | Upgrade diagnostic/wireshark to version 2.2.8-0.175.3.24.0.1.0 on Solaris 11.3Upgrade diagnostic/wireshark/wireshark-common to version 2.2.8-0.175.3.24.0.1.0 on Solaris 11.3Upgrade diagnostic/wireshark/tshark to version 2.2.8-0.175.3.24.0.1.0 on Solaris 11.3 | Sep 19, 2017 | Jul 18, 2017 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Jul 18, 2017 |
| Suse | — | Upgrade libwiretap10Upgrade libwiretap7Upgrade libwsutil11Upgrade wireshark-gtkUpgrade libwireshark9Upgrade libwsutil8Upgrade libwireshark8Upgrade libwiretap6Upgrade libwsutil7Upgrade wiresharkUpgrade libwireshark13Upgrade wireshark-develUpgrade wireshark-ui-qtUpgrade libwscodecs1 | Jul 26, 2017 | Jul 18, 2017 |
| Ubuntu | — | Upgrade wireshark | Nov 19, 2024 | Jul 18, 2017 |
| Wireshark | — | Upgrade to Wireshark version 2.0.14Upgrade to Wireshark version 2.2.8 | Oct 4, 2017 | Jul 18, 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