Keepalived Keepalived
6 CVEs affecting Keepalived Keepalived. Latest disclosed: 2021-11-26. Critical: 1, High: 1.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2018-19115 | Critical | 9.8 | 2018-11-08 | keepalived before 2.0.7 has a heap-based buffer overflow when parsing HTTP status codes resulting in DoS or possibly unspecified other impact, because extract_… |
CVE-2018-19045 | High | 7.5 | 2018-11-08 | keepalived 2.0.8 used mode 0666 when creating new temporary files upon a call to PrintData or PrintStats, potentially leaking sensitive information. |
CVE-2021-44225 | Medium | 5.4 | 2021-11-26 | In Keepalived through 2.2.4, the D-Bus policy does not sufficiently restrict the message destination, allowing any user to inspect and manipulate any property… |
CVE-2018-19046 | Medium | 4.7 | 2018-11-08 | 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 pr… |
CVE-2018-19044 | Medium | 4.7 | 2018-11-08 | keepalived 2.0.8 didn't check for pathnames with symlinks when writing data to a temporary file upon a call to PrintData or PrintStats. This allowed local user… |
CVE-2011-1784 | | 2011-05-20 | The pidfile_write function in core/pidfile.c in keepalived 1.2.2 and earlier uses 0666 permissions for the (1) keepalived.pid, (2) checkers.pid, and (3) vrrp.p… |