Low: libpcap security, bug fix, and enhancement update
Summary
ALSA-2020:4547: Low: libpcap security, bug fix, and enhancement update. Affects libpcap-devel versions < 14:1.9.1-4.el8. Fixed in 14:1.9.1-4.el8. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The libpcap packages provide a portable framework for low-level network monitoring. The libpcap library offers network statistics collection, security monitoring, and network debugging capabilities.
Vulnerability Detail
A resource exhaustion vulnerability (CVE-2019-15165) has been identified in libpcap. This vulnerability occurs during PHB header length validation, potentially leading to resource exhaustion. An attacker could exploit this vulnerability to cause a denial-of-service condition or execute arbitrary code.
How To Fix
Minimum fixed version
14:1.9.1-4.el8
This is the first release that contains the fix.
sudo dnf update libpcap-develTip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability.
Conclusion
In conclusion, the libpcap package has been updated to address a resource exhaustion vulnerability. It is recommended to upgrade to the latest version to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for libpcap-devel →
FAQ
libpcap is a portable framework for low-level network monitoring, providing network statistics collection, security monitoring, and network debugging capabilities.
This vulnerability could lead to resource exhaustion, potentially causing a denial-of-service condition or enabling an attacker to execute arbitrary code.
To fix this vulnerability, upgrade the libpcap package to version 1.9.1 or later.
No, there is no known workaround for this vulnerability.
You can find more information about this vulnerability in the CVE page(s) listed in the References section.
