CVE-2018-19115 json
keepalived before 2.0.7 has a heap-based buffer overflow when parsing HTTP status codes resulting in DoS or possibly unspecified other impa…
published 8y ago modified 4mo ago also EUVD-2018-10828
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.7%
- EPSS 3.7% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
keepalived before 2.0.7 has a heap-based buffer overflow when parsing HTTP status codes resulting in DoS or possibly unspecified other impact, because extract_status_code in lib/html.c has no validation of the status code and instead writes an unlimited amount of data to the heap.
Patch / fix
- keepalived keepalived 2.0.7
- keepalived Debian 14, Debian 13, Debian 12 1:2.0.10-1
debian advisories DEBIAN-CVE-2018-19115
- keepalived Ubuntu 16.04 LTS 1:1.2.24-1ubuntu0.16.04.2
- keepalived Ubuntu 18.04 LTS 1:1.3.9-1ubuntu0.18.04.2
- keepalived Ubuntu Pro 14.04 LTS 1:1.2.7-1ubuntu1+esm1
ubuntu advisories UBUNTU-CVE-2018-19115
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
- keepalived RHEL 7 1.3.5-8.el7_6
- keepalived RHEL 7.4 EUS 1.3.5-1.el7_4.1
- keepalived RHEL 7.5 EUS 1.3.5-7.el7_5.2
red hat advisories RHSA-2019:1945RHSA-2019:1792RHSA-2019:0022
- github.com/acassen/keepalived#961 commit
- github.com/acassen/keepalived#961 pull request
Is CVE-2018-19115 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2018-19115 updated cvss 8.1
keepalived: Heap-based buffer overflow when parsing HTTP status codes allows for denial of service or possibly arbitrary code execution
-
Red Hat Enterprise Linux 6 keepalivedaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux for ARM and IBM Power LE (POWER9) Server (v. 7) keepalived 1.3.5-8.el7_6 Red Hat Enterprise Linux Server (v. 7) keepalived 1.3.5-8.el7_6fixed: vendor fix RHSA-2019:0022
-
Red Hat Enterprise Linux Server EUS (v. 7.4) keepalived 1.3.5-1.el7_4.1fixed: vendor fix RHSA-2019:1945
-
Red Hat Enterprise Linux Server EUS (v. 7.5) keepalived 1.3.5-7.el7_5.2fixed: vendor fix RHSA-2019:1792
-
Red Hat Enterprise Linux Workstation (v. 7) keepalived 1.3.5-8.el7_6fixed: vendor fix RHSA-2019:0022
-
Red Hat Enterprise Linux 8 keepalivednot affected: vulnerable code not present
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
Exploit prediction
3.75% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
github.com
/acassen/keepalived/pull/961/commits/f28015671a4b04785859d1b4b1327b367b6a10e9
patch, third-party-advisory
-
github.com
/acassen/keepalived/pull/961
patch, third-party-advisory
-
security.gentoo.org
/glsa/201903-01
vendor-advisory, third-party-advisory
-
access.redhat.com
/errata/RHSA-2019:0022
vendor-advisory, third-party-advisory
-
usn.ubuntu.com
/3995-1/
vendor-advisory
-
usn.ubuntu.com
/3995-2/
vendor-advisory
-
access.redhat.com
/errata/RHSA-2019:1792
vendor-advisory
-
access.redhat.com
/errata/RHSA-2019:1945
vendor-advisory
-
lists.debian.org
/debian-lts-announce/2018/11/msg00034.html
mailing-list, third-party-advisory
-
bugzilla.suse.com
/show_bug.cgi?id=1015141
issue-tracking, third-party-advisory
Sources
- CVE List CVE-2018-19115
- NVD CVE-2018-19115
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.