wnpa-sec-2017-28 · openSAFETY dissector memory exhaustion


Name: openSAFETY dissector memory exhaustion

Docid: wnpa-sec-2017-28

Date: June 1, 2017

Affected versions: 2.2.0 to 2.2.7, 2.0.0 to 2.0.13

Fixed versions: 2.2.8, 2.0.14

Wireshark bug 13649
Wireshark bug 13755



The openSAFETY dissector could crash or exhaust system memory. Discovered by the OSS-Fuzz project.


It may be possible to make Wireshark crash or 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.2.8, 2.0.14 or later.

Update: July 18, 2017

Updated for Wireshark 2.2.8 and 2.0.14. Added bug 13755.
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