Name: MS-WSP dissector excessive memory consumption
Date: April 21, 2021
Affected versions: 3.4.0 to 3.4.4, 3.2.0 to 3.2.12
Fixed versions: 3.4.5, 3.2.13
The MS-WSP dissector could consume excessive amounts of 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 3.4.5, 3.2.13 or later.