Количество 11
Количество 11
CVE-2023-7256
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.
CVE-2023-7256
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.
CVE-2023-7256
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.
CVE-2023-7256
CVE-2023-7256
In affected libpcap versions during the setup of a remote packet captu ...
ROS-20240918-11
Уязвимость libpcap
GHSA-7m22-9mw3-j4pp
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.
BDU:2024-07427
Уязвимость функции freeaddrinfo() библиотеки libpcap, позволяющая нарушителю вызвать отказ в обслуживании
SUSE-SU-2024:3355-1
Security update for libpcap
SUSE-SU-2024:3217-1
Security update for libpcap
SUSE-SU-2024:3210-1
Security update for libpcap
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2023-7256 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. | CVSS3: 4.4 | 0% Низкий | 10 месяцев назад |
 | CVE-2023-7256 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. | CVSS3: 4.4 | 0% Низкий | 10 месяцев назад |
 | CVE-2023-7256 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. | CVSS3: 4.4 | 0% Низкий | 10 месяцев назад |
 | CVSS3: 4.4 | 0% Низкий | 8 месяцев назад | |
| CVE-2023-7256 In affected libpcap versions during the setup of a remote packet captu ... | CVSS3: 4.4 | 0% Низкий | 10 месяцев назад |
 | ROS-20240918-11 Уязвимость libpcap | CVSS3: 4.4 | 0% Низкий | 9 месяцев назад |
| GHSA-7m22-9mw3-j4pp 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. | CVSS3: 4.4 | 0% Низкий | 10 месяцев назад |
 | BDU:2024-07427 Уязвимость функции freeaddrinfo() библиотеки libpcap, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 4.4 | 0% Низкий | 10 месяцев назад |
 | SUSE-SU-2024:3355-1 Security update for libpcap | 9 месяцев назад | ||
| SUSE-SU-2024:3217-1 Security update for libpcap | 10 месяцев назад | ||
| SUSE-SU-2024:3210-1 Security update for libpcap | 10 месяцев назад |
Уязвимостей на страницу