Due to failure in validating the length provided by an attacker-crafted MSMMS packet, Wireshark version 4.0.5 and prior, in an unusual configuration, is susceptible to a heap-based buffer overflow, and possibly code execution in the context of the process running Wireshark
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
The product writes data past the end, or before the beginning, of the intended buffer.
| Link | Tags |
|---|---|
| https://takeonme.org/cves/CVE-2023-0667.html | third party advisory exploit |
| https://gitlab.com/wireshark/wireshark/-/issues/19086 | issue tracking exploit |
| https://security.gentoo.org/glsa/202309-02 | third party advisory |