SUSE-RU-2024:0259-1: Recommended update for pacemaker
This update for pacemaker fixes the following issues: libcrmcommon: wait for reply from appropriate controller commands (bsc#1218312, rh#2225631, rh#2221084) attrd: don't start a new election when receiving a client update (bsc#1215446)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
suse/pacemaker-libsto a version that resolves this vulnerability.Fixed in 2.1.5 - Upgrade
Upgrade
suse/pacemaker-debuginfoto a version that resolves this vulnerability.Fixed in 2.1.5 - Upgrade
Upgrade
suse/pacemaker-debugsourceto a version that resolves this vulnerability.Fixed in 2.1.5 - Upgrade
Upgrade
suse/pacemaker-develto a version that resolves this vulnerability.Fixed in 2.1.5 - Upgrade
Upgrade
suse/pacemaker-remote-debuginfoto a version that resolves this vulnerability.Fixed in 2.1.5 - Upgrade
Upgrade
suse/pacemaker-clito a version that resolves this vulnerability.Fixed in 2.1.5 - Upgrade
Upgrade
suse/pacemakerto a version that resolves this vulnerability.Fixed in 2.1.5 - Upgrade
Upgrade
suse/pacemaker-remoteto a version that resolves this vulnerability.Fixed in 2.1.5 - Upgrade
Upgrade
suse/pacemaker-cli-debuginfoto a version that resolves this vulnerability.Fixed in 2.1.5 - Upgrade
Upgrade
suse/pacemaker-libs-debuginfoto a version that resolves this vulnerability.Fixed in 2.1.5 - Upgrade
Upgrade
suse/pacemaker-ctsto a version that resolves this vulnerability.Fixed in 2.1.5 - Upgrade
Upgrade
pacemakerto a version that resolves this vulnerability.Patch SUSE-2024-259=1 - Upgrade
Upgrade
pacemakerto a version that resolves this vulnerability.Patch openSUSE-SLE-15.5-2024-259=1 - Upgrade
Upgrade
pacemakerto a version that resolves this vulnerability.Patch SUSE-SLE-Product-HA-15-SP5-2024-259=1
Event History
Frequently Asked Questions
Which deployments should prioritize this update?
Systems running Pacemaker or Pacemaker Remote, including installations using the listed pacemaker libraries or command-line components, should assess and apply the update. The advisory identifies fixes in controller command reply handling and attrd election behavior.
Are any specific attacker prerequisites or affected default configurations documented?
No attacker prerequisites, attack vector, or default-configuration conditions are provided in the available advisory data.
What can be done if the update cannot be installed immediately?
The provided data does not specify mitigations or workarounds. Review the affected Pacemaker components in use and plan deployment of the recommended update.