Overview 15 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 1 EPSS ≥ 0.5
15matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
2public PoC13.3%
1EPSS ≥ 0.56.7%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
15
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
15
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
2
13.3%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
13
86.7%
split by
peak 4 / year
20042
Not applicable2
Medium2
not blocked2
Working exploit published1
No public exploit1
20050
20060
20071
Not applicable1
Medium1
not blocked1
No public exploit1
20080
20090
20100
20110
20120
20130
20140
20152
Not applicable2
Medium2
not blocked2
Working exploit published1
No public exploit1
20160
20171
Not applicable1
Medium1
not blocked1
No public exploit1
20181
Not applicable1
Medium1
not blocked1
No public exploit1
20194
Not applicable4
Medium4
not blocked4
No public exploit4
20200
20210
20221
Not applicable1
Medium1
not blocked1
No public exploit1
20231
Not applicable1
Medium1
not blocked1
No public exploit1
20242
Not applicable2
Medium2
not blocked2
No public exploit2
20042006200820102012201420162018202020222024
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-8006 | Medium | 2024-08-31 | Not applicable | No public exploit | 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-2023-7256 | Medium | 2024-08-31 | Not applicable | No public exploit | 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-1801 | Medium | 2023-04-07 | Not applicable | No public exploit | The SMB protocol decoder in tcpdump version 4.99.3 can perform an out-of-bounds write when decoding a crafted network packet. |
| CVE-2021-41043 | Medium | 2022-01-05 | Not applicable | No public exploit | Use after free in tcpslice triggers AddressSanitizer, no other confirmed impact. |
| CVE-2019-15165 | Medium | 2019-10-03 | Not applicable | No public exploit | sf-pcapng.c in libpcap before 1.9.1 does not properly validate the PHB header length before allocating memory. |
| CVE-2019-15164 | Medium | 2019-10-03 | Not applicable | No public exploit | rpcapd/daemon.c in libpcap before 1.9.1 allows SSRF because a URL may be provided as a capture source. |
| CVE-2019-15162 | Medium | 2019-10-03 | Not applicable | No public exploit | rpcapd/daemon.c in libpcap before 1.9.1 on non-Windows platforms provides details about why authentication failed, which might make it easier for attackers to enumerate valid usernames. |
| CVE-2019-15161 | Medium | 2019-10-03 | Not applicable | No public exploit | rpcapd/daemon.c in libpcap before 1.9.1 mishandles certain length values because of reuse of a variable. This may open up an attack vector involving extra data at the end of a request. |
| CVE-2018-19519 | Medium | 2018-11-25 | Not applicable | No public exploit | In tcpdump 4.9.2, a stack-based buffer over-read exists in the print_prefix function of print-hncp.c via crafted packet data because of missing initialization. |
| CVE-2017-16808 | Medium | 2017-11-13 | Not applicable | No public exploit | tcpdump before 4.9.3 has a heap-based buffer over-read related to aoe_print in print-aoe.c and lookup_emem in addrtoname.c. |
| CVE-2015-2154 | Medium | 2015-03-24 | Not applicable | No public exploit | The osi_print_cksum function in print-isoclns.c in the ethernet printer in tcpdump before 4.7.2 allows remote attackers to cause a denial of service (out-of-bounds read and crash) via a crafted (1) length, (2) offset, or (3) base pointer checksum value. |
| CVE-2015-2153 | Medium | 2015-03-24 | Not applicable | Working exploit published | The rpki_rtr_pdu_print function in print-rpki-rtr.c in the TCP printer in tcpdump before 4.7.2 allows remote attackers to cause a denial of service (out-of-bounds read or write and crash) via a crafted header length in an RPKI-RTR Protocol Data Unit (PDU). |
| CVE-2007-1218 | Medium | 2007-03-02 | Not applicable | No public exploit | Off-by-one buffer overflow in the parse_elements function in the 802.11 printer code (print-802_11.c) for tcpdump 3.9.5 and earlier allows remote attackers to cause a denial of service (crash) via a crafted 802.11 frame. NOTE: this was originally referred to as heap-based, but it might be stack-based. |
| CVE-2004-0184 | Medium | 2004-05-04 | Not applicable | Working exploit published | Integer underflow in the isakmp_id_print for TCPDUMP 3.8.1 and earlier allows remote attackers to cause a denial of service (crash) via an ISAKMP packet with an Identification payload with a length that becomes less than 8 during byte order conversion, which causes an out-of-bounds read, as demonstrated by the Striker ISAKMP Protocol Test Suite. |
| CVE-2004-0183 | Medium | 2004-05-04 | Not applicable | No public exploit | TCPDUMP 3.8.1 and earlier allows remote attackers to cause a denial of service (crash) via ISAKMP packets containing a Delete payload with a large number of SPI's, which causes an out-of-bounds read, as demonstrated by the Striker ISAKMP Protocol Test Suite. |