SSRF Vulnerability in libpcap: Remote Capture Source Exploitation Risk

libpcap Updated 02 Oct 2025

Summary

03/10/2019
N/A
Yes i
Medium
5.3

ALPINE-CVE-2019-15164: rpcapd/daemon.c in libpcap before 1.9.1 allows SSRF because a URL may be provided as a capture source. Affects libpcap versions < 1.1.1-r0. Fixed in 1.1.1-r0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

libpcap is a widely-used library for network packet capture, enabling applications to capture and analyze network traffic. It provides a portable framework for capturing network packets across various operating systems. The library is essential for network monitoring tools, intrusion detection systems, and other applications that require packet analysis. However, a vulnerability in libpcap prior to version 1.9.1 allows for Server-Side Request Forgery (SSRF) attacks, where an attacker can exploit the library's handling of URLs as capture sources.

Vulnerability Detail

The vulnerability identified as CVE-2019-15164 exists in the rpcapd daemon of libpcap before version 1.9.1. It allows an attacker to provide a URL as a capture source, which can lead to SSRF. This means that the attacker could potentially make requests to internal services or resources that should not be accessible from the outside, leading to unauthorized access or data leakage. The technical aspect of this vulnerability lies in the improper validation of user input, which fails to restrict the capture source to legitimate network interfaces.

How To Fix

Minimum fixed version

1.1.1-r0

This is the first release that contains the fix.

sudo apk add --upgrade libpcap

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, it is advisable to restrict access to the rpcapd service or to disable it if it is not in use. This can be done by stopping the service with the command: 'service rpcapd stop'. Additionally, ensure that any user input for capture sources is strictly validated to prevent unauthorized URLs.

Conclusion

The SSRF vulnerability in libpcap (CVE-2019-15164) poses a significant risk to applications that utilize this library for network packet capture. It is crucial to update to the patched version to safeguard against potential exploitation. Users are encouraged to monitor their applications for vulnerabilities using tools like Vulert, which can provide real-time alerts without requiring code access.

See every vulnerability recorded for libpcap →

Share this vulnerability

FAQ

CVE-2019-15164 is a vulnerability in libpcap that allows for Server-Side Request Forgery (SSRF) due to improper handling of URLs as capture sources.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which analyzes your manifest file for vulnerabilities.

SSRF vulnerabilities can lead to unauthorized access to internal services, data leakage, and potential exploitation of other vulnerabilities within the network.

Yes, the vulnerability has been patched in libpcap version 1.9.1 and later. It is recommended to update to this version or higher.

If immediate updating is not possible, consider disabling the rpcapd service or implementing strict input validation to mitigate the risk.

Related vulnerabilities

Recent vulnerabilities recorded for libpcap.

How To Fix

Minimum fixed version

1.1.1-r0

This is the first release that contains the fix.

sudo apk add --upgrade libpcap

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback