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

> A bug in Pacemaker prevents resource status detection during node shutdown, potentially affecting cluster availability and requiring a patch.

- **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:** 18 May 2021

## What is ALBA-2021:1996?

ALBA-2021:1996 is a vulnerability in pacemaker, published on 18 May 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):

* crm_mon not able to detect resource-status when used in stop-operation of
a Resource Agent during node shutdown (BZ#1951098)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pacemaker` | AlmaLinux:8 | All versions | 2.0.5-9.el8_4.1 |
| `pacemaker-cli` | AlmaLinux:8 | All versions | 2.0.5-9.el8_4.1 |
| `pacemaker-cts` | AlmaLinux:8 | All versions | 2.0.5-9.el8_4.1 |
| `pacemaker-doc` | AlmaLinux:8 | All versions | 2.0.5-9.el8_4.1 |
| `pacemaker-libs-devel` | AlmaLinux:8 | All versions | 2.0.5-9.el8_4.1 |
| `pacemaker-nagios-plugins-metadata` | AlmaLinux:8 | All versions | 2.0.5-9.el8_4.1 |
| `pacemaker-remote` | AlmaLinux:8 | All versions | 2.0.5-9.el8_4.1 |

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

Apply the vendor's patch.

## Is ALBA-2021:1996 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2021:1996 is a vulnerability in pacemaker, published on 18 May 2021. 
Exploitation: There is no known exploitation of ALBA-2021:1996 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-1996/ (Markdown: https://insights.sbomify.com/ALBA-2021-1996/index.md)
```

## Sources

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

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