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.
Metrics
Affected Vendors & Products
References
History
Wed, 09 Sep 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-772 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Tue, 08 Sep 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 07 Sep 2026 08:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tcpdump
Tcpdump libpcap |
|
| Vendors & Products |
Tcpdump
Tcpdump libpcap |
Sat, 05 Sep 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | rpcapd memory leak in libpcap before 1.10.7 | |
| Weaknesses | CWE-401 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: Tcpdump
Published: 2026-09-05T18:51:32.438Z
Updated: 2026-09-08T15:16:52.614Z
Reserved: 2026-07-29T17:47:46.571Z
Link: CVE-2026-18313
Updated: 2026-09-08T15:16:48.581Z
Status : Awaiting Analysis
Published: 2026-09-05T19:16:55.590
Modified: 2026-09-08T19:20:25.117
Link: CVE-2026-18313