CVE-2019-15165
Published: 30 September 2019
sf-pcapng.c in libpcap before 1.9.1 does not properly validate the PHB header length before allocating memory.
Notes
Author | Note |
---|---|
sbeattie | this is likely actually fixed by 617b12c0339db4891d117b661982126c495439ea see github issue about CVE ID confusion but whatever, can't get a straight answer out of upstream, so will use this CVE ID for the issue that touches sf-pcapng.c |
Priority
Status
Package | Release | Status |
---|---|---|
libpcap Launchpad, Ubuntu, Debian |
bionic |
Released
(1.8.1-6ubuntu1.18.04.1)
|
disco |
Released
(1.8.1-6ubuntu1.19.04.1)
|
|
eoan |
Not vulnerable
(1.9.1-2)
|
|
trusty |
Released
(1.5.3-2ubuntu0.1)
Available with Ubuntu Pro or Ubuntu Pro (Infra-only) |
|
upstream |
Released
(1.9.1-1)
|
|
xenial |
Released
(1.7.4-2ubuntu0.1)
|
|
Patches: upstream: https://github.com/the-tcpdump-group/libpcap/commit/a5a36d9e82dde7265e38fe1f87b7f11c461c29f6 upstream: https://github.com/the-tcpdump-group/libpcap/commit/87d6bef033062f969e70fa40c43dfd945d5a20ab |
Severity score breakdown
Parameter | Value |
---|---|
Base score | 5.3 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | None |
Integrity impact | Low |
Availability impact | None |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |