Описание
rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use. A malicious client can cause the server to leak memory substantially faster.
A flaw was found in libpcap, specifically within the rpcapd daemon. This vulnerability allows a remote attacker to cause a denial of service (DoS) by sending specially crafted RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ messages. The rpcapd daemon allocates memory for these messages but fails to free it, leading to a memory leak. Over time, this can exhaust available memory, making the service unavailable.
Отчет
This Moderate impact memory leak in the rpcapd daemon, part of libpcap, can lead to a denial of service on Red Hat systems. A remote attacker with low privileges can send specially crafted RPCAP messages, causing rpcapd to continuously allocate memory without freeing it. This can exhaust system resources, rendering the service unavailable. The vulnerability is present when the rpcapd service is running and accessible over the network.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 10 | libpcap | Fix deferred | ||
| Red Hat Enterprise Linux 6 | libpcap | Fix deferred | ||
| Red Hat Enterprise Linux 7 | libpcap | Fix deferred | ||
| Red Hat Enterprise Linux 8 | libpcap | Fix deferred | ||
| Red Hat Enterprise Linux 9 | libpcap | Fix deferred | ||
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Fix deferred | ||
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Fix deferred |
Показывать по
Дополнительная информация
Статус:
EPSS
4.3 Medium
CVSS3
Связанные уязвимости
rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use. A malicious client can cause the server to leak memory substantially faster.
rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use. A malicious client can cause the server to leak memory substantially faster.
rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_ ...
rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use. A malicious client can cause the server to leak memory substantially faster.
EPSS
4.3 Medium
CVSS3