Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.5

Wireshark may freeze when processing crafted packets

CVE-2017-7746 · published 9 years ago
Summary

Versions of Wireshark from 2.0.0 to 2.0.11 and 2.2.0 to 2.2.5 can get stuck in a loop if they encounter specially crafted network data or a corrupted capture file. This can cause the program to become unresponsive. Updating to a newer version of Wireshark resolves the issue.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
wireshark wireshark 2.0.0
2.0.1
2.0.2
2.0.3
2.0.4
2.0.5
2.0.6
2.0.7
2.0.8
2.0.9
2.0.10
2.0.11
6 more version ranges
cpe:2.3:a:wireshark:wireshark:2.0.0:*:*:*:*:*:*:*
debian debian_linux 8.0
cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
Original advisory text
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/...
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
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker partial control (estimated)
Severity
7.5 High
Exploitation
2% chance of attack within 30 days
Type
CWE-835Loop with Unreachable Exit Condition ('Infinite Loop')
Timeline
Published12 Apr 2017
Updated29 Oct 2026
First seen29 Sep 2026
Sources
CVE-2017-7746 · NVD
Track software like this
Free during beta