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

Wireshark 1.12‑1.12.4 can be slowed by specific traffic

CVE-2015-3810 · published 11 years ago
Summary

The WebSocket analysis code in Wireshark versions 1.12 up to 1.12.4 can get stuck in a loop when it processes a specially crafted WebSocket packet. This consumes a lot of CPU, making the application unresponsive and preventing packet analysis. Upgrade to Wireshark 1.12.5 or later, or apply the vendor's patch, to stop the problem.

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 1.12.0
1.12.1
1.12.2
1.12.3
1.12.4
cpe:2.3:a:wireshark:wireshark:1.12.0:*:*:*:*:*:*:*
Original advisory text
epan/dissectors/packet-websocket.c in the WebSocket dissector in Wireshark 1.12.x before 1.12.5 uses a recursive algorithm, which allows remote attackers to cause a denial of service (CPU consumpti...
epan/dissectors/packet-websocket.c in the WebSocket dissector in Wireshark 1.12.x before 1.12.5 uses a recursive algorithm, which allows remote attackers to cause a denial of service (CPU consumption) via a crafted packet.
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.8 High
Exploitation
3% chance of attack within 30 days
Type
CWE-399Resource Management Errors
Timeline
Published26 May 2015
Updated23 Oct 2026
First seen29 Sep 2026
Sources
CVE-2015-3810 · NVD
Track software like this
Free during beta