In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the DICOM dissector could go into a large or infinite loop. This was addressed in epan/dissectors/packet-dcm.c by preventing an offset overflow.
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
| Link | Tags |
|---|---|
| http://www.securitytracker.com/id/1041608 | vdb entry third party advisory |
| https://www.wireshark.org/security/wnpa-sec-2018-39.html | vendor advisory |
| https://lists.debian.org/debian-lts-announce/2018/07/msg00045.html | third party advisory mailing list |
| https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=2e716c32be6aa20e1813b0002878853e71f8b2f4 | |
| https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14742 | issue tracking vendor advisory |
| http://www.securityfocus.com/bid/104847 | vdb entry third party advisory |
| http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00027.html | vendor advisory |