# SUSE-SU-2022:2325-1: Security update for resource-agents

> An attacker with local access can read sensitive data from predictable log files in the mariadb resource agent.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jul 2022

## What is SUSE-SU-2022:2325-1?

SUSE-SU-2022:2325-1 is a vulnerability in resource-agents, published on 7 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This update for resource-agents fixes the following issues:

- Fixed predictable log file in /tmp in mariadb.in (bsc#1146691).
- Allow aws-vpc-move-ip to specify an interface label to distinguish the IP address (bsc#1199766)
- Implement options to disable DAD and to allow sending NA in the background (bsc#1196164)
- Imporove error message if monpassword was not set (bsc#1197956)

## Which versions are affected by SUSE-SU-2022:2325-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `resource-agents` | SUSE:Linux Enterprise High Availability Extension 15 SP4 | All versions | 4.10.0+git40.0f4de473-150400.3.7.1 |
| `resource-agents` | openSUSE:Leap 15.4 | All versions | 4.10.0+git40.0f4de473-150400.3.7.1 |

## How do I fix SUSE-SU-2022:2325-1?

Apply the vendor's patch.

## Is SUSE-SU-2022:2325-1 being exploited?

There is no known exploitation of SUSE-SU-2022:2325-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2022:2325-1 and fix it if it is affected.

What it is: SUSE-SU-2022:2325-1 is a vulnerability in resource-agents, published on 7 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2022:2325-1 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/SUSE-SU-2022-2325-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2022-2325-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2022:2325-1

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