The Quarterly Threat Landscape Report is out. See what attackers are targeting now.Read report
In Wireshark 3.2.x before 3.2.1, the WASSP dissector could crash. This was addressed in epan/dissectors/packet-wassp.c by using >= and <= to resolve off-by-one errors.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade wireshark | Jul 30, 2024 | Jan 16, 2020 |
| Oracle Solaris | — | Upgrade diagnostic/wireshark/wireshark-common to version 2.6.14-11.4.18.0.1.3.0 on Solaris 11.4Upgrade diagnostic/wireshark/tshark to version 2.6.14-11.4.18.0.1.3.0 on Solaris 11.4Upgrade diagnostic/wireshark to version 2.6.14-11.4.18.0.1.3.0 on Solaris 11.4 | Jan 19, 2021 | Jan 16, 2020 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Jan 16, 2020 |
| Suse | — | Upgrade wireshark-develUpgrade libmaxminddb-develUpgrade libspandsp2Upgrade wiresharkUpgrade spandsp-develUpgrade spandsp-docUpgrade libwireshark13Upgrade mmdblookupUpgrade wireshark-ui-qtUpgrade libmaxminddb0Upgrade libspandsp2-32bitUpgrade libmaxminddb0-32bitUpgrade libwsutil11Upgrade libwiretap10 | Mar 17, 2020 | Jan 16, 2020 |
| Wireshark | — | Upgrade to Wireshark version 3.2.1 | Jan 16, 2020 | Jan 16, 2020 |
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