keepalived 2.0.8 didn't check for pathnames with symlinks when writing data to a temporary file upon a call to PrintData or PrintStats.
keepalived 2.0.8 didn't check for pathnames with symlinks when writing data to a temporary file upon a call to PrintData or PrintStats. This allowed local users to overwrite arbitrary files if fs.protected_symlinks is set to 0, as demonstrated by a symlink from /tmp/keepalived.data or /tmp/keepalived.stats to /etc/passwd.
- Published
- Nov 8, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 40th percentile
- CWE
- CWE-59
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| keepalived | keepalived | cpe:2.3:a:keepalived:keepalived |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- keepalived keepalived2.0.8
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 |
| openSUSE:Tumbleweed | keepalived | before 2.2.2-4.2 | 2.2.2-4.2 |
| Red Hat:enterprise_linux:7::server | keepalived | before 0:1.3.5-16.el7 | 0:1.3.5-16.el7 |
| Red Hat:enterprise_linux:7::server | keepalived-debuginfo | before 0:1.3.5-16.el7 | 0:1.3.5-16.el7 |
| SUSE:Linux Enterprise High Availability Extension 15 SP1 | keepalived | before 2.0.19-3.3.1 | 2.0.19-3.3.1 |
Same product
keepalived: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-19115keepalived before 2.0.7 has a heap-based buffer overflow when parsing HTTP status codes resulting in DoS or possibly unspecified other impac40Plan
- 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-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) |
| opensuse:keepalived | 2.2.2-4.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:keepalived | 0:1.3.5-16.el7 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:keepalived-debuginfo | 0:1.3.5-16.el7 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| suse:keepalived | 2.0.19-3.3.1 · SUSE:Linux Enterprise High Availability Extension 15 SP1 | 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
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-59 · Improper Link Resolution Before File Access ('Link Following')CVSS vector
CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
Attack patterns (CAPEC)
ATT&CK techniques
- Obfuscated Files or Information: HTML SmugglingT1027.006
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Autostart Execution:Shortcut ModificationT1547.009
- Hide Artifacts: Resource ForkingT1564.009
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: Services File Permissions WeaknessT1574.010
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:2285
- bugzilla.suse.com/show_bug.cgi?id=1015141
- github.com/acassen/keepalived/commit/04f2d32871bb3b11d7dc024039952f2fe2750306
- security.gentoo.org/glsa/201903-01
Vendor advisories and official records. Exploit/PoC links are deliberately left out.