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 Details
- CVSS 3.1 Base Score: 4.7
- CVSS 3.0 Vector: (CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N)
Covered by Rapid7
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade keepalived | Jan 10, 2019 | Nov 8, 2018 |
| Debian | — | Upgrade keepalived | Jul 30, 2024 | Nov 8, 2018 |
| Gentoo Linux | — | Upgrade sys-cluster/keepalived. | Mar 11, 2019 | Nov 8, 2018 |
| Huawei Euleros 2_0_sp5 | — | Upgrade keepalived | Sep 3, 2020 | Nov 8, 2018 |
| Huawei Euleros 2_0_sp8 | — | Upgrade keepalived | Mar 24, 2020 | Nov 8, 2018 |
| Suse | — | Upgrade keepalived | Dec 22, 2018 | Nov 8, 2018 |
| Ubuntu | — | No solution exists | Jun 26, 2025 | Nov 8, 2018 |
| Vmware Photon_os | — | Use 'tdnf update' to upgrade all packages to the latest version. | Jan 20, 2025 | Nov 8, 2018 |
Prioritise with Active Threat Intelligence
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub