# ALBA-2021:1088: pacemaker bug fix and enhancement update

> Pacemaker updates fix bugs causing invalid XML generation and bundle promotion issues, potentially affecting cluster availability.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 6 Apr 2021

## What is ALBA-2021:1088?

ALBA-2021:1088 is a vulnerability in pacemaker, published on 6 Apr 2021. 

### Official description

The Pacemaker cluster resource manager is a collection of technologies
working together to maintain data integrity and application availability in
the event of failures.

Bug Fix(es) and Enhancement(s):

* pacemaker never promotes a bundle until another transition unblocks it
(BZ#1935240)

* pacemaker generates invalid xml for certain failures (BZ#1939533)

## Which versions are affected by ALBA-2021:1088?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pacemaker` | AlmaLinux:8 | All versions | 2.0.4-6.el8_3.2 |
| `pacemaker-cli` | AlmaLinux:8 | All versions | 2.0.4-6.el8_3.2 |
| `pacemaker-cts` | AlmaLinux:8 | All versions | 2.0.4-6.el8_3.2 |
| `pacemaker-doc` | AlmaLinux:8 | All versions | 2.0.4-6.el8_3.2 |
| `pacemaker-libs-devel` | AlmaLinux:8 | All versions | 2.0.4-6.el8_3.2 |
| `pacemaker-nagios-plugins-metadata` | AlmaLinux:8 | All versions | 2.0.4-6.el8_3.2 |
| `pacemaker-remote` | AlmaLinux:8 | All versions | 2.0.4-6.el8_3.2 |

## How do I fix ALBA-2021:1088?

Apply the vendor's patch.

## Is ALBA-2021:1088 being exploited?

There is no known exploitation of ALBA-2021:1088 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALBA-2021:1088 and fix it if it is affected.

What it is: ALBA-2021:1088 is a vulnerability in pacemaker, published on 6 Apr 2021. 
Exploitation: There is no known exploitation of ALBA-2021:1088 in the wild and no public exploit code.

Affected product: pacemaker. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/ALBA-2021-1088/ (Markdown: https://insights.sbomify.com/ALBA-2021-1088/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2021:1088

---
From sbomify Insights: https://insights.sbomify.com/ALBA-2021-1088/
Summaries are generated and may contain mistakes; the official description above is the record.