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-11.html Upstream bug(s): https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15553
Created wireshark tracking bugs for this issue: Affects: fedora-all [bug 1697962]
Upstream patch: https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=355fe663408695e4191fde9404cc97bd41f6834d
Statement: This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 8 as they did not include the vulnerable functions.
External References: https://www.wireshark.org/security/wnpa-sec-2019-11.html