Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2018-19044: 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.

MediumCVSS 4.7 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.50% (FIRST EPSS).
  • 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.
  • Fixed version: keepalived (Alpine:v3.10) 2.0.11-r0; keepalived (Debian:12) 1:2.0.10-1; keepalived (openSUSE:Tumbleweed) 2.2.2-4.2.

Low priority for now. Upgrade to keepalived (Alpine:v3.10) 2.0.11-r0; keepalived (Debian:12) 1:2.0.10-1; keepalived (openSUSE:Tumbleweed) 2.2.2-4.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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% · 43th percentile

Report tools

JSON

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%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2018-19044

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
keepalivedkeepalived

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.

EcosystemPackageAffected rangeFix
Alpine:v3.10keepalivedbefore 2.0.11-r02.0.11-r0
Debian:12keepalivedbefore 1:2.0.10-11:2.0.10-1
openSUSE:Tumbleweedkeepalivedbefore 2.2.2-4.22.2.2-4.2
Red Hat:enterprise_linux:7::serverkeepalivedbefore 0:1.3.5-16.el70:1.3.5-16.el7
Red Hat:enterprise_linux:7::serverkeepalived-debuginfobefore 0:1.3.5-16.el70:1.3.5-16.el7
SUSE:Linux Enterprise High Availability Extension 15 SP1keepalivedbefore 2.0.19-3.3.12.0.19-3.3.1

Other 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…
    40Plan
  • CVE-2018-19045keepalived 2.0.8 used mode 0666 when creating new temporary files upon a call to PrintData or PrintStats, potentially leaking sensitive…
    31Monitor
  • 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…
    21Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2011-1784May 20, 2011 · The 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
  • Later →CVE-2018-19046Nov 8, 2018 · keepalived 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

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:keepalived2.0.11-r0 · Alpine:v3.10Package registry (OSV)
debian:keepalived1:2.0.10-1 · Debian:12Package registry (OSV)
opensuse:keepalived2.2.2-4.2 · openSUSE:TumbleweedPackage registry (OSV)
red hat:keepalived0:1.3.5-16.el7 · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:keepalived-debuginfo0:1.3.5-16.el7 · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
suse:keepalived2.0.19-3.3.1 · SUSE:Linux Enterprise High Availability Extension 15 SP1Package 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.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

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

CVSS vector

CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N

nvd-primary

References

All records