It may be possible to make Wireshark before version 3.4.10 consume excessive CPU resources by injecting a malformed Bluetooth DHT packet onto the wire or by convincing someone to read a malformed packet trace file.
It may be possible to make Wireshark before version 3.4.10 consume excessive CPU resources by injecting a malformed Bluetooth DHT packet onto the wire or by convincing someone to read a malformed packet trace file.
https://www.wireshark.org/security/wnpa-sec-2021-10 https://gitlab.com/wireshark/wireshark/-/issues/17677 https://gitlab.com/wireshark/wireshark/-/merge_requests/4815 https://gitlab.com/wireshark/wireshark/-/commit/d3c762dcb634fcca070deed1f5d17b791ce84166
Vulmon