An issue has been found in the openSAFETY dissector of Wireshark < 2.2.7, where an over-sized memory allocation can be triggered by injecting a malicious packet into the wire or by convincing someone to read a malformed packet trace file.
An issue has been found in the openSAFETY dissector of Wireshark < 2.2.7, where an over-sized memory allocation can be triggered by injecting a malicious packet into the wire or by convincing someone to read a malformed packet trace file.
https://www.wireshark.org/security/wnpa-sec-2017-28.html https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13649