A security issue has been found in the WBXML dissector of wireshark <= 2.2.7. It is 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.
A security issue has been found in the WBXML dissector of wireshark <= 2.2.7. It is 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.
https://www.wireshark.org/security/wnpa-sec-2017-13.html https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13477 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13796