CVE-2021-44225
CVE-2021-44225 is a medium-severity vulnerability in Keepalived with a CVSS 3.x base score of 5.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.
Key facts
- Severity: Medium (CVSS 3.x base score 5.4)
- CVSS v2: 5.5
- EPSS exploit prediction: 1% (63rd percentile)
- Actively exploited: Not listed in CISA KEV
- Affected product: Keepalived
- Published:
- Last modified:
Description
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. This leads to access-control bypass in some situations in which an unrelated D-Bus system service has a settable (writable) property
Frequently asked questions
- What is 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. This leads to access-control bypass in some situations in which an unrelated D-Bus system service has a settable (writable) property
- How severe is CVE-2021-44225?
- CVE-2021-44225 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.
- Is CVE-2021-44225 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (63rd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2021-44225?
- CVE-2021-44225 primarily affects Keepalived. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2021-44225?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2021-44225 published?
- CVE-2021-44225 was published on 2021-11-26 and last updated on 2026-06-17.
References
- https://github.com/acassen/keepalived/commit/7977fec0be89ae6fe87405b3f8da2f0b5e415e3d
- https://github.com/acassen/keepalived/pull/2063
- https://lists.debian.org/debian-lts-announce/2023/04/msg00012.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/5226RYNMNB7FL4MSJDIBBGPUWH6LMRYV/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6O2R6EXURJQFPFPYFWRCZLUYVWQCLSZM/
Affected products (3)
- cpe:2.3:a:keepalived:keepalived:*:*:*:*:*:*:*:*
- cpe:2.3:o:fedoraproject:fedora:34:*:*:*:*:*:*:*
- cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*
More vulnerabilities in Keepalived
- CVE-2018-19115 — Critical (CVSS 9.8): keepalived before 2.0.7 has a heap-based buffer overflow when parsing HTTP status codes resulting in DoS or possibly…
- CVE-2018-19045 — High (CVSS 7.5): keepalived 2.0.8 used mode 0666 when creating new temporary files upon a call to PrintData or PrintStats, potentially…
- CVE-2018-19046 — Medium (CVSS 4.7): keepalived 2.0.8 didn't check for existing plain files when writing data to a temporary file upon a call to PrintData…
- CVE-2018-19044 — Medium (CVSS 4.7): keepalived 2.0.8 didn't check for pathnames with symlinks when writing data to a temporary file upon a call to…
- CVE-2011-1784 — Low (CVSS 3.6): The pidfile_write function in core/pidfile.c in keepalived 1.2.2 and earlier uses 0666 permissions for the (1)…