# SUSE-SU-2020:1092-1: Security update for resource-agents

> Attackers can exploit unsafe tempfile usage and default passwords in resource-agents to escalate privileges or bypass security controls on SUSE systems.

- **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:** 23 Apr 2020

## What is SUSE-SU-2020:1092-1?

SUSE-SU-2020:1092-1 is a vulnerability in resource-agents, published on 23 Apr 2020. 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 multiple vulnerabilities related to unsafe tempfile usage.
  (bsc#1146690 bsc#1146691 bsc#1146776 bsc#1146784 bsc#1146785 bsc#1146787 bsc#1146789)
- Fixed issues where the ocfmon user was created with a default password (bsc#1021689, bsc#1146687).

## Which versions are affected by SUSE-SU-2020:1092-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `resource-agents` | SUSE:Linux Enterprise High Availability Extension 12 SP3 | All versions | 4.0.1+git.1495055229.643177f1-2.45.1 |

## How do I fix SUSE-SU-2020:1092-1?

Apply the vendor's patch.

## Is SUSE-SU-2020:1092-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2020:1092-1 is a vulnerability in resource-agents, published on 23 Apr 2020. 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-2020:1092-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-2020-1092-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2020-1092-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2020:1092-1

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