CVE-2023-7256: Double-free in libpcap before 1.10.5 with remote packet capture support.
Double-free in libpcap before 1.10.5 with remote packet capture support.
Other sources
In affected libpcap versions during the setup of a remote packet capture the internal function sockinitaddress() calls getaddrinfo() and possibly freeaddrinfo(), but does not clearly indicate to the caller function whether freeaddrinfo() still remains to be called after the function returns. This makes it possible in some scenarios that both the function and its caller call freeaddrinfo() for the same allocated memory block. A similar problem was reported in Apple libpcap, to which Apple assigned CVE-2023-40400.
— MITRE
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2023-7256?
CVE-2023-7256 is rated as a moderate severity vulnerability affecting certain versions of libpcap.
How do I fix CVE-2023-7256?
To remediate CVE-2023-7256, upgrade to a version of libpcap that is 1.10.5 or higher.
What versions of libpcap are affected by CVE-2023-7256?
CVE-2023-7256 affects libpcap versions prior to 1.10.5.
What functionality is compromised in CVE-2023-7256?
CVE-2023-7256 compromises the proper management of memory in the function sock_initaddress due to unclear handling of freeaddrinfo.
Is remote exploitation possible with CVE-2023-7256?
Yes, CVE-2023-7256 can potentially lead to memory-related issues during remote packet capture setup.