Skip to content
Fencer Intel
medium 5.3

CVE-2019-15165 json

sf-pcapng.c in libpcap before 1.9.1 does not properly validate the PHB header length before allocating memory.

published 7y ago modified 4mo ago also EUVD-2019-6221

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

sf-pcapng.c in libpcap before 1.9.1 does not properly validate the PHB header length before allocating memory.

Patch / fix

  • tcpdump libpcap 1.9.1
  • apple mac_os_x 10.13.6
  • libpcap Debian 14, Debian 13, Debian 12 1.9.1-1

debian advisories DEBIAN-CVE-2019-15165

  • libpcap Ubuntu 16.04 LTS 1.7.4-2ubuntu0.1
  • libpcap Ubuntu 18.04 LTS 1.8.1-6ubuntu1.18.04.1
  • libpcap Ubuntu Pro 14.04 LTS 1.5.3-2ubuntu0.1

ubuntu advisories UBUNTU-CVE-2019-15165

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libpcap RHEL 8 14:1.9.1-4.el8

red hat advisories RHSA-2020:4547

  • libpcap SLE Module for Basesystem 15 SP1, SLE Module for Basesystem 15 1.8.1-4.3.1
  • libpcap SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES for SAP 12 SP3 +20 more 1.8.1-10.3.1
  • tcpdump SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES for SAP 12 SP3 +16 more 4.9.2-14.14.1

suse advisories SUSE-SU-2019:2673-1SUSE-SU-2019:2669-1

  • libpcap openSUSE Leap 15.1 1.8.1-lp151.4.3.1
  • libpcap openSUSE Leap 15.0 1.8.1-lp150.3.3.1

opensuse advisories openSUSE-SU-2019:2345-1openSUSE-SU-2019:2343-1

  • libpcap Alpine 3.10 1.1.1-r0
  • libpcap Alpine 3.24, Alpine 3.23, Alpine 3.22 +10 more 1.9.1-r0

alpine advisories ALPINE-CVE-2019-15165

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2019-15165 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-15165 updated cvss 7.5

libpcap: Resource exhaustion during PHB header length validation

  • Red Hat Enterprise Linux 6 libpcap
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 libpcap
    affected: no fix available “Fix deferred”
  • Red Hat CodeReady Linux Builder (v. 8) libpcap-devel 1.9.1-4.el8, libpcap-debuginfo 1.9.1-4.el8, libpcap-debugsource 1.9.1-4.el8 Red Hat Enterprise Linux BaseOS (v. 8) libpcap 1.9.1-4.el8
    fixed: vendor fix RHSA-2020:4547

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
11mo ago

Exploit prediction

2.83% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.