In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length.
References
Link | Resource |
---|---|
https://www.wireshark.org/security/wnpa-sec-2017-19.html | Vendor Advisory |
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=58e69cc769dea24b721abd8a29f9eedc11024b7e | Issue Tracking Patch Vendor Advisory |
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13576 | Issue Tracking Vendor Advisory Patch |
http://www.securityfocus.com/bid/97635 | Third Party Advisory VDB Entry |
https://lists.debian.org/debian-lts-announce/2019/01/msg00010.html | Mailing List Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Information
Published : 2017-04-12 16:59
Updated : 2019-10-02 17:03
NVD link : CVE-2017-7746
Mitre link : CVE-2017-7746
JSON object : View
CWE
CWE-835
Loop with Unreachable Exit Condition ('Infinite Loop')
Products Affected
debian
- debian_linux
wireshark
- wireshark