In Wireshark 2.2.0 to 2.2.4 and 2.0.0 to 2.0.10, there is a WSP infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wsp.c by validating the capability length.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Link | Tags |
---|---|
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13348 | patch vendor advisory issue tracking |
https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=62afef41277dfac37f515207ca73d33306e3302b | |
http://www.securityfocus.com/bid/96564 | third party advisory vdb entry |
https://www.wireshark.org/security/wnpa-sec-2017-05.html | vendor advisory |
http://www.debian.org/security/2017/dsa-3811 | third party advisory vendor advisory |