CVE-2018-19046

Description

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.

Category

4.7
CVSS
Severity: Medium
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.15%
Vendor Advisory gentoo.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://security.gentoo.org/glsa/201903-01 third party advisory vendor advisory
https://bugzilla.suse.com/show_bug.cgi?id=1015141 issue tracking third party advisory
https://github.com/acassen/keepalived/issues/1048 third party advisory patch

Frequently Asked Questions

What is the severity of CVE-2018-19046?
CVE-2018-19046 has been scored as a medium severity vulnerability.
How to fix CVE-2018-19046?
To fix CVE-2018-19046, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2018-19046 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2018-19046 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.