wnpa-sec-2016-47 · OpenFlow long loop


Name: OpenFlow long loop

Docid: wnpa-sec-2016-47

Date: July 27, 2016

Affected versions: 2.0.0 to 2.0.4, 1.12.0 to 1.12.12

Fixed versions: 2.0.5, 1.12.13

Wireshark bug 12659



The OpenFlow dissector (and possibly others) could go into a long loop. Discovered by Antti Levomäki.


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 2.0.5, 1.12.13 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