CVE-2018-19046
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…
Does this matter?
Lower severity and a low EPSS score (0.37%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.0
- 4.7 MEDIUMCVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
- EPSS
- 0.37% probability · 30th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-200
- Affected
- keepalived/keepalived
- Source
- cve@mitre.org
References
- https://bugzilla.suse.com/show_bug.cgi?id=1015141Issue Tracking, Third Party Advisory
- https://github.com/acassen/keepalived/issues/1048Patch, Third Party Advisory
- https://security.gentoo.org/glsa/201903-01Third Party Advisory
- https://bugzilla.suse.com/show_bug.cgi?id=1015141Issue Tracking, Third Party Advisory
- https://github.com/acassen/keepalived/issues/1048Patch, Third Party Advisory
- https://security.gentoo.org/glsa/201903-01Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.