In Wireshark 2.2.0 to 2.2.3 and 2.0.0 to 2.0.9, the ASTERIX dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-asterix.c by changing a data type to avoid an integer 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 |
|---|---|
| https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=781f03580c81339513bb1238b202b72469a1240b | |
| http://www.securityfocus.com/bid/95795 | vdb entry third party advisory |
| https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13344 | issue tracking patch vdb entry third party advisory |
| https://www.wireshark.org/security/wnpa-sec-2017-01.html | vendor advisory |
| http://www.debian.org/security/2017/dsa-3811 | vendor advisory |
| https://code.wireshark.org/review/#/c/19746/ | patch vendor advisory |
| http://www.securitytracker.com/id/1037694 | vdb entry |