# ALBA-2022:0347: resource-agents bug fix and enhancement update

> Bug fixes for GCP resource agents prevent restart failures and permission errors in high-availability environments.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Feb 2022

## What is ALBA-2022:0347?

ALBA-2022:0347 is a vulnerability in resource-agents, published on 1 Feb 2022. 

### Official description

The resource-agents packages provide the Pacemaker and RGManager service
managers with a set of scripts. These scripts interface with several
services to allow operating in a high-availability (HA) environment.

Bug Fix(es) and Enhancement(s):

* gcp-vpc-move-vip, gcp-vpc-move-route, gcp-pd-move: A failed API call
returns OCF_ERR_CONFIGURED, preventing restarts (BZ#2008955)

* gcp-vpc-move-route and gcp-vpc-move-vip can fail with permission denied
errors if token file is not found (BZ#2011839)

## Which versions are affected by ALBA-2022:0347?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `resource-agents` | AlmaLinux:8 | All versions | 4.1.1-98.el8_5.2 |
| `resource-agents-aliyun` | AlmaLinux:8 | All versions | 4.1.1-98.el8_5.2 |
| `resource-agents-gcp` | AlmaLinux:8 | All versions | 4.1.1-98.el8_5.2 |
| `resource-agents-paf` | AlmaLinux:8 | All versions | 4.1.1-98.el8_5.2 |

## How do I fix ALBA-2022:0347?

Apply the vendor's patch.

## Is ALBA-2022:0347 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2022:0347 is a vulnerability in resource-agents, published on 1 Feb 2022. 
Exploitation: There is no known exploitation of ALBA-2022:0347 in the wild and no public exploit code.

Affected product: resource-agents. 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-2022-0347/ (Markdown: https://insights.sbomify.com/ALBA-2022-0347/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2022:0347

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