First published: Fri Aug 30 2024(Updated: )
In affected libpcap versions during the setup of a remote packet capture the internal function sock_initaddress() 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.
Credit: security@tcpdump.org
Affected Software | Affected Version | How to fix |
---|---|---|
libpcap | <1.10.5 |
Upgrade to libpcap 1.10.5.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-7256 is rated as a moderate severity vulnerability affecting certain versions of libpcap.
To remediate CVE-2023-7256, upgrade to a version of libpcap that is 1.10.5 or higher.
CVE-2023-7256 affects libpcap versions prior to 1.10.5.
CVE-2023-7256 compromises the proper management of memory in the function sock_initaddress due to unclear handling of freeaddrinfo.
Yes, CVE-2023-7256 can potentially lead to memory-related issues during remote packet capture setup.