Headline
CVE-2020-25866: BLIP: Static decompression buffer is of insufficient size (#16866) · Issues · Wireshark Foundation / wireshark · GitLab
In Wireshark 3.2.0 to 3.2.6 and 3.0.0 to 3.0.13, the BLIP protocol dissector has a NULL pointer dereference because a buffer was sized for compressed (not uncompressed) messages. This was addressed in epan/dissectors/packet-blip.c by allowing reasonable compression ratios and rejecting ZIP bombs.
Summary
Currently the BLIP dissector uses a statically allocated buffer of 16 Kb in order to store the results of decompressing a compressed message body. However, the 16 Kb figure is the maximum size of a compressed message frame, not an uncompressed one, so any body that has an uncompressed message larger than 16Kb will crash wireshark
Steps to reproduce
The easiest thing to do is to open the attached capture file
What is the current bug behavior?
Wireshark crashes
What is the expected correct behavior?
Wireshark correctly displays the > 16Kb decompressed body
Sample capture file
badtrace.pcapng.gz
Relevant logs and/or screenshots
No relevant logs, the crash is very straightforward
Build information
Version 3.2.6 (v3.2.6-0-g4f9257fb)
Related news
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). The supported version that is affected is Prior to 6.1.18. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data. CVSS 3.1 Base Score 6.0 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N).