keepalived before 2.0.7 has a heap-based buffer overflow when parsing HTTP status codes resulting in DoS or possibly unspecified other impac
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.
- Published
- Nov 8, 2018
- Updated
- Jun 16, 2026
- EPSS
- 3.7% · 89th percentile
- CWE
- CWE-787
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.7%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| keepalived | keepalived | cpe:2.3:a:keepalived:keepalived |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| redhat | enterprise linux server | cpe:2.3:o:redhat:enterprise_linux_server |
| redhat | enterprise linux server aus | cpe:2.3:o:redhat:enterprise_linux_server_aus |
| redhat | enterprise linux server eus | cpe:2.3:o:redhat:enterprise_linux_server_eus |
| redhat | enterprise linux server tus | cpe:2.3:o:redhat:enterprise_linux_server_tus |
| redhat | enterprise linux workstation | cpe:2.3:o:redhat:enterprise_linux_workstation |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux8.0
- keepalived keepalivedbefore 2.0.7
- redhat enterprise linux server7.0
- redhat enterprise linux server aus7.6
- redhat enterprise linux server eus7.6
- redhat enterprise linux server tus7.6
- redhat enterprise linux workstation7.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | keepalived | before 1:2.0.10-1 | 1:2.0.10-1 |
| Debian:8 | keepalived | before 1:1.2.13-1+deb8u1 | 1:1.2.13-1+deb8u1 |
| Red Hat:enterprise_linux:7::server | keepalived | before 0:1.3.5-8.el7_6 | 0:1.3.5-8.el7_6 |
| Red Hat:enterprise_linux:7::server | keepalived-debuginfo | before 0:1.3.5-8.el7_6 | 0:1.3.5-8.el7_6 |
| Red Hat:rhel_eus:7.4::server | keepalived | before 0:1.3.5-1.el7_4.1 | 0:1.3.5-1.el7_4.1 |
| Red Hat:rhel_eus:7.4::server | keepalived-debuginfo | before 0:1.3.5-1.el7_4.1 | 0:1.3.5-1.el7_4.1 |
| Red Hat:rhel_eus:7.5::server | keepalived | before 0:1.3.5-7.el7_5.2 | 0:1.3.5-7.el7_5.2 |
| Red Hat:rhel_eus:7.5::server | keepalived-debuginfo | before 0:1.3.5-7.el7_5.2 | 0:1.3.5-7.el7_5.2 |
Same product
keepalived: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-19045keepalived 2.0.8 used mode 0666 when creating new temporary files upon a call to PrintData or PrintStats, potentially leaking sensitive info31Monitor
- CVE-2021-44225In Keepalived through 2.2.4, the D-Bus policy does not sufficiently restrict the message destination, allowing any user to inspect and manip21Monitor
- CVE-2018-19046keepalived 2.0.8 didn't check for existing plain files when writing data to a temporary file upon a call to PrintData or PrintStats.18Monitor
- CVE-2018-19044keepalived 2.0.8 didn't check for pathnames with symlinks when writing data to a temporary file upon a call to PrintData or PrintStats.18Monitor
- CVE-2011-1784The pidfile_write function in core/pidfile.c in keepalived 1.2.2 and earlier uses 0666 permissions for the (1) keepalived.pid, (2) checkers.14Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:keepalived | 1:2.0.10-1 · Debian:12 | Package registry (OSV) |
| red hat:keepalived | 0:1.3.5-8.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:keepalived-debuginfo | 0:1.3.5-8.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- access.redhat.com/errata/RHSA-2019:0022
- access.redhat.com/errata/RHSA-2019:1792
- access.redhat.com/errata/RHSA-2019:1945
- bugzilla.suse.com/show_bug.cgi?id=1015141
- github.com/acassen/keepalived/pull/961
- github.com/acassen/keepalived/pull/961/commits/f28015671a4b04785859d1b4b1327b367b6a10e9
- lists.debian.org/debian-lts-announce/2018/11/msg00034.html
- security.gentoo.org/glsa/201903-01
- usn.ubuntu.com/3995-1/
- usn.ubuntu.com/3995-2/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.