Mageia 2024-0295: libpcap Security Advisory Updates
Summary
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. (CVE-2023-7256)
Remote packet capture support is disabled by default in libpcap. When a
user builds libpcap with remote packet capture support enabled, one of
the functions that become available is pcap_findalldevs_ex(). One of the
function arguments can be a filesystem path, which normally means a
directory with input data files. When the specified path cannot be used
as a directory, the function receives NULL from opendir(), but does not
check the return value and passes the NULL value to readdir(), which
causes a NULL pointer derefence. (CVE-2024-8006)
References
- https://bugs.mageia.org/show_bug.cgi?id=33537
- https://lwn.net/Articles/988357/
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-7256
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-8006
Resolution
MGASA-2024-0295 - Updated libpcap packages fix security vulnerabilities
SRPMS
- 9/core/libpcap-1.10.5-1.mga9
