Due to failure in validating the length provided by an attacker-crafted RTPS packet, Wireshark version 4.0.5 and prior, by default, 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-0666.html | third party advisory exploit |
| https://gitlab.com/wireshark/wireshark/-/issues/19085 | issue tracking exploit |
| https://www.wireshark.org/docs/relnotes/wireshark-4.0.6.html | release notes |
| https://www.wireshark.org/security/wnpa-sec-2023-18.html | vendor advisory |
| https://www.debian.org/security/2023/dsa-5429 | third party advisory |
| https://security.gentoo.org/glsa/202309-02 | third party advisory |