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.
References
Link | Resource |
---|---|
https://bugzilla.suse.com/show_bug.cgi?id=1015141 | Issue Tracking Third Party Advisory |
https://github.com/acassen/keepalived/issues/1048 | Patch Third Party Advisory |
https://security.gentoo.org/glsa/201903-01 | Third Party Advisory |
https://bugzilla.suse.com/show_bug.cgi?id=1015141 | Issue Tracking Third Party Advisory |
https://github.com/acassen/keepalived/issues/1048 | Patch Third Party Advisory |
https://security.gentoo.org/glsa/201903-01 | Third Party Advisory |
Configurations
History
21 Nov 2024, 03:57
Type | Values Removed | Values Added |
---|---|---|
References | () https://bugzilla.suse.com/show_bug.cgi?id=1015141 - Issue Tracking, Third Party Advisory | |
References | () https://github.com/acassen/keepalived/issues/1048 - Patch, Third Party Advisory | |
References | () https://security.gentoo.org/glsa/201903-01 - Third Party Advisory |
Information
Published : 2018-11-08 20:29
Updated : 2024-11-21 03:57
NVD link : CVE-2018-19046
Mitre link : CVE-2018-19046
CVE.ORG link : CVE-2018-19046
JSON object : View
Products Affected
keepalived
- keepalived
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor