Libpcap vulnerabilitiesRanked by how likely they are to be used.
Libpcap is made by Tcpdump. We track 8 published vulnerabilities in it, across 40 versions. None of them is on the list of flaws known to be exploited today. If you run Libpcap, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Libpcap vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Libpcap's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Libpcap flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 4.4%CVE-2019-15163High
rpcapd/daemon.c in libpcap before 1.9.1 allows attackers to cause a denial of service (NULL pointer dereference and daemon crash) if a crypt() call fails.
- 3.6%CVE-2011-1935Critical
pcap-linux.c in libpcap 1.1.1 before commit ea9432fabdf4b33cbc76d9437200e028f1c47c93 when snaplen is set may truncate packets, which might allow remote attackers to send arbitrary data while avoiding detection via...
- 2.9%CVE-2019-15164Medium
rpcapd/daemon.c in libpcap before 1.9.1 allows SSRF because a URL may be provided as a capture source.
- 2.8%CVE-2019-15165Medium
sf-pcapng.c in libpcap before 1.9.1 does not properly validate the PHB header length before allocating memory.
- 2.8%CVE-2019-15161Medium
rpcapd/daemon.c in libpcap before 1.9.1 mishandles certain length values because of reuse of a variable.
- 1.8%CVE-2019-15162Medium
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.
- 0.2%CVE-2023-7256Medium
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...
- 0.2%CVE-2024-8006Medium
Remote packet capture support is disabled by default in libpcap.
Running Libpcap? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
rpcapd/daemon.c in libpcap before 1.9.1 allows attackers to cause a denial of service (NULL pointer dereference and daemon crash) if a crypt() call fails.
- Matched to
- Libpcap on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 8 published vulnerabilities listed under the name Libpcap, across 40 versions.
None of Libpcap's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Libpcap. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.