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. If a local attacker had previously created a file with the expected name (e.g., /tmp/keepalived.data or /tmp/keepalived.stats), with read access for the attacker and write access for the keepalived process, then this potentially leaked sensitive information.
Advisories
Source ID Title
EUVD EUVD EUVD-2018-10764 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. If a local attacker had previously created a file with the expected name (e.g., /tmp/keepalived.data or /tmp/keepalived.stats), with read access for the attacker and write access for the keepalived process, then this potentially leaked sensitive information.
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-05T11:30:04.013Z

Reserved: 2018-11-06T00:00:00

Link: CVE-2018-19046

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2018-11-08T20:29:00.510

Modified: 2024-11-21T03:57:13.227

Link: CVE-2018-19046

cve-icon Redhat

Severity : Moderate

Publid Date: 2018-11-08T00:00:00Z

Links: CVE-2018-19046 - Bugzilla

cve-icon OpenCVE Enrichment

No data.