CVE-2022-0581
wireshark: Crash in the CMS protocol dissector in Wireshark 3.6.0 to 3.6.1 and 3.4.0 to 3.4.11 allows denial of service via pack...
CVE-2022-0581 is fixed in 17 products on 1 platform, first by libwireshark-data 2.6.10-1~ubuntu18.04.0+esm2, released February 14, 2022. It is not reported as exploited. Patch Radar priority: High.
High
CVSS
7.5
high
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0179
78th percentile
Crash in the CMS protocol dissector in Wireshark 3.6.0 to 3.6.1 and 3.4.0 to 3.4.11 allows denial of service via packet injection or crafted capture file
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| libwireshark-data · Ubuntu 18.04.6 LTS (bionic) | 2.6.10-1~ubuntu18.04.0+esm2 | libwireshark-data 2.6.10-1~ubuntu18.04.0+esm2 | Feb 14, 2022 |
| libwireshark-data · Ubuntu 20.04 LTS (focal) | 3.2.3-1ubuntu0.1~esm2 | libwireshark-data 3.2.3-1ubuntu0.1~esm2 | Feb 18, 2022 |
| libwireshark11 · Ubuntu 18.04.6 LTS (bionic) | 2.6.10-1~ubuntu18.04.0+esm2 | libwireshark11 2.6.10-1~ubuntu18.04.0+esm2 | Feb 14, 2022 |
| libwireshark13 · Ubuntu 20.04 LTS (focal) | 3.2.3-1ubuntu0.1~esm2 | libwireshark13 3.2.3-1ubuntu0.1~esm2 | Feb 18, 2022 |
| libwiretap10 · Ubuntu 20.04 LTS (focal) | 3.2.3-1ubuntu0.1~esm2 | libwiretap10 3.2.3-1ubuntu0.1~esm2 | Feb 18, 2022 |
| libwiretap8 · Ubuntu 18.04.6 LTS (bionic) | 2.6.10-1~ubuntu18.04.0+esm2 | libwiretap8 2.6.10-1~ubuntu18.04.0+esm2 | Feb 14, 2022 |
| libwscodecs2 · Ubuntu 18.04.6 LTS (bionic) | 2.6.10-1~ubuntu18.04.0+esm2 | libwscodecs2 2.6.10-1~ubuntu18.04.0+esm2 | Feb 14, 2022 |
| libwsutil11 · Ubuntu 20.04 LTS (focal) | 3.2.3-1ubuntu0.1~esm2 | libwsutil11 3.2.3-1ubuntu0.1~esm2 | Feb 18, 2022 |
| libwsutil9 · Ubuntu 18.04.6 LTS (bionic) | 2.6.10-1~ubuntu18.04.0+esm2 | libwsutil9 2.6.10-1~ubuntu18.04.0+esm2 | Feb 14, 2022 |
| tshark · Ubuntu 18.04.6 LTS (bionic) | 2.6.10-1~ubuntu18.04.0+esm2 | tshark 2.6.10-1~ubuntu18.04.0+esm2 | Feb 14, 2022 |
| tshark · Ubuntu 20.04 LTS (focal) | 3.2.3-1ubuntu0.1~esm2 | tshark 3.2.3-1ubuntu0.1~esm2 | Feb 18, 2022 |
| wireshark · Debian 12.15 (bookworm) | 3.6.2-1 | DEBIAN-CVE-2022-0581 | Feb 14, 2022 |
| wireshark · Debian 13.5 (trixie) | 3.6.2-1 | DEBIAN-CVE-2022-0581 | Feb 14, 2022 |
| wireshark · Debian 14 | 3.6.2-1 | DEBIAN-CVE-2022-0581 | Feb 14, 2022 |
| wireshark · Ubuntu 18.04.6 LTS (bionic) | 2.6.10-1~ubuntu18.04.0+esm2 | wireshark 2.6.10-1~ubuntu18.04.0+esm2 | Feb 14, 2022 |
| wireshark · Ubuntu 20.04 LTS (focal) | 3.2.3-1ubuntu0.1~esm2 | wireshark 3.2.3-1ubuntu0.1~esm2 | Feb 18, 2022 |
| wireshark-cli · amzn 2023 | 1:4.0.2-1.amzn2023.0.2 | ALAS2023-2023-038 | Feb 17, 2023 |
| wireshark-cli-debuginfo · amzn 2023 | 1:4.0.2-1.amzn2023.0.2 | ALAS2023-2023-038 | Feb 17, 2023 |
| wireshark-common · Ubuntu 18.04.6 LTS (bionic) | 2.6.10-1~ubuntu18.04.0+esm2 | wireshark-common 2.6.10-1~ubuntu18.04.0+esm2 | Feb 14, 2022 |
| wireshark-common · Ubuntu 20.04 LTS (focal) | 3.2.3-1ubuntu0.1~esm2 | wireshark-common 3.2.3-1ubuntu0.1~esm2 | Feb 18, 2022 |
| wireshark-debugsource · amzn 2023 | 1:4.0.2-1.amzn2023.0.2 | ALAS2023-2023-038 | Feb 17, 2023 |
| wireshark-devel · amzn 2023 | 1:4.0.2-1.amzn2023.0.2 | ALAS2023-2023-038 | Feb 17, 2023 |
| wireshark-gtk · Ubuntu 18.04.6 LTS (bionic) | 2.6.10-1~ubuntu18.04.0+esm2 | wireshark-gtk 2.6.10-1~ubuntu18.04.0+esm2 | Feb 14, 2022 |
| wireshark-gtk · Ubuntu 20.04 LTS (focal) | 3.2.3-1ubuntu0.1~esm2 | wireshark-gtk 3.2.3-1ubuntu0.1~esm2 | Feb 18, 2022 |
| wireshark-qt · Ubuntu 18.04.6 LTS (bionic) | 2.6.10-1~ubuntu18.04.0+esm2 | wireshark-qt 2.6.10-1~ubuntu18.04.0+esm2 | Feb 14, 2022 |
| wireshark-qt · Ubuntu 20.04 LTS (focal) | 3.2.3-1ubuntu0.1~esm2 | wireshark-qt 3.2.3-1ubuntu0.1~esm2 | Feb 18, 2022 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.