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.
{
"extracted_events": [
{
"cpe": "cpe:2.3:a:keepalived:keepalived:2.0.8:*:*:*:*:*:*:*",
"range": [
{
"introduced": "2.0.8"
},
{
"last_affected": "2.0.8"
}
],
"source": "CPE_STRING"
}
]
}