libwireshark11: Multiple memory leaks in the x11_init_protocol function in epan/dissectors/packet-x11.c in the X11 dissector in Wires...
CVE-2015-3812 is fixed in 10 products on 1 platform, first by libwireshark-data 2.6.3-1~ubuntu18.04.1, released August 29, 2018. It is not reported as exploited. Patch Radar priority: Routine.
Multiple memory leaks in the x11_init_protocol function in epan/dissectors/packet-x11.c in the X11 dissector in Wireshark 1.10.x before 1.10.14 and 1.12.x before 1.12.5 allow remote attackers to cause a denial of service (memory consumption) via a crafted packet.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| libwireshark-data · Ubuntu 18.04.6 LTS (bionic) | 2.6.3-1~ubuntu18.04.1 | libwireshark-data 2.6.3-1~ubuntu18.04.1 | Aug 29, 2018 |
| libwireshark11 · Ubuntu 18.04.6 LTS (bionic) | 2.6.3-1~ubuntu18.04.1 | libwireshark11 2.6.3-1~ubuntu18.04.1 | Aug 29, 2018 |
| libwiretap8 · Ubuntu 18.04.6 LTS (bionic) | 2.6.3-1~ubuntu18.04.1 | libwiretap8 2.6.3-1~ubuntu18.04.1 | Aug 29, 2018 |
| libwscodecs2 · Ubuntu 18.04.6 LTS (bionic) | 2.6.3-1~ubuntu18.04.1 | libwscodecs2 2.6.3-1~ubuntu18.04.1 | Aug 29, 2018 |
| libwsutil9 · Ubuntu 18.04.6 LTS (bionic) | 2.6.3-1~ubuntu18.04.1 | libwsutil9 2.6.3-1~ubuntu18.04.1 | Aug 29, 2018 |
| tshark · Ubuntu 18.04.6 LTS (bionic) | 2.6.3-1~ubuntu18.04.1 | tshark 2.6.3-1~ubuntu18.04.1 | Aug 29, 2018 |
| wireshark · Ubuntu 18.04.6 LTS (bionic) | 2.6.3-1~ubuntu18.04.1 | wireshark 2.6.3-1~ubuntu18.04.1 | Aug 29, 2018 |
| wireshark-common · Ubuntu 18.04.6 LTS (bionic) | 2.6.3-1~ubuntu18.04.1 | wireshark-common 2.6.3-1~ubuntu18.04.1 | Aug 29, 2018 |
| wireshark-gtk · Ubuntu 18.04.6 LTS (bionic) | 2.6.3-1~ubuntu18.04.1 | wireshark-gtk 2.6.3-1~ubuntu18.04.1 | Aug 29, 2018 |
| wireshark-qt · Ubuntu 18.04.6 LTS (bionic) | 2.6.3-1~ubuntu18.04.1 | wireshark-qt 2.6.3-1~ubuntu18.04.1 | Aug 29, 2018 |
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.