wnpa-sec-2013-31 · ETCH dissector large loop


Name: ETCH dissector large loop

Docid: wnpa-sec-2013-31

Date: May 17, 2013

Affected versions: 1.8.0 to 1.8.6

Fixed versions: 1.8.7

Wireshark bug 8464



The ETCH dissector could go into a large loop. Discovered by Moshe Kaplan.


It may be possible to make Wireshark consume excessive CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.


Upgrade to Wireshark 1.8.7 or later.

Go Beyond with Riverbed Technology

Riverbed is Wireshark's primary sponsor and provides our funding. They also make great products that fully integrate with Wireshark.

I have a lot of traffic...

ANSWER: SteelCentral™ AppResponse 11
  • • Full stack analysis – from packets to pages
  • • Rich performance metrics & pre-defined insights for fast problem identification/resolution
  • • Modular, flexible solution for deeply-analyzing network & application performance
Learn More