Vulnerabilities > Keepalived
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2021-11-26 | CVE-2021-44225 | 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. | 5.4 |
| 2018-11-08 | CVE-2018-19115 | Out-of-bounds Write vulnerability in multiple products 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_status_code in lib/html.c has no validation of the status code and instead writes an unlimited amount of data to the heap. | 7.5 |
| 2018-11-08 | CVE-2018-19046 | Information Exposure vulnerability in Keepalived 2.0.8 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. | 1.9 |
| 2018-11-08 | CVE-2018-19045 | Information Exposure vulnerability in Keepalived 2.0.8 keepalived 2.0.8 used mode 0666 when creating new temporary files upon a call to PrintData or PrintStats, potentially leaking sensitive information. | 5.0 |
| 2018-11-08 | CVE-2018-19044 | Link Following vulnerability in Keepalived 2.0.8 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. | 3.3 |
| 2011-05-20 | CVE-2011-1784 | Permissions, Privileges, and Access Controls vulnerability in Keepalived 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.pid files in /var/run/, which allows local users to kill arbitrary processes by writing a PID to one of these files. | 3.6 |