Name: X11 memory leak
Date: May 12, 2015
Affected versions: 1.12.0 to 1.12.4, 1.10.0 to 1.10.13
Fixed versions: 1.12.5, 1.10.14
The X11 dissector could leak memory.
It may be possible to make Wireshark consume excessive CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.
Upgrade to Wireshark 1.12.5, 1.10.14 or later.