Name: DICOM dissector large loop
Date: July 18, 2018
Affected versions: 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, 2.2.0 to 2.2.15
Fixed versions: 2.6.2, 2.4.8, 2.2.16
The DICOM dissector could go into a large or infinite loop.
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 2.6.2, 2.4.8, 2.2.16 or later.