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 External Referencies: https://www.wireshark.org/security/wnpa-sec-2019-12.html Upstream bug(s): https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15585
Created wireshark tracking bugs for this issue: Affects: fedora-all [bug 1697956]
Upstream patch: https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=5d9d7893d6723b4545d4c2c765002e4830493dc6
Statement: This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 8 as they did not include support for Osmocom Generic Subscriber Update Protocol (GSUP).
External References: https://www.wireshark.org/security/wnpa-sec-2019-12.html