# SUSE-SU-2022:2547-2: Security update for logrotate

> Attackers can exploit improper coredump handling in SUID binaries to escalate privileges on affected Linux 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:** 25 Jul 2022

## What is SUSE-SU-2022:2547-2?

SUSE-SU-2022:2547-2 is a vulnerability in logrotate, published on 25 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 logrotate fixes the following issues:

Security issues fixed:

- Improved coredump handing for SUID binaries (bsc#1192449).

Non-security issues fixed:

- Fixed 'logrotate emits unintended warning: keyword size not properly separated, found 0x3d' (bsc#1200278, bsc#1200802).

## Which versions are affected by SUSE-SU-2022:2547-2?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `logrotate` | openSUSE:Leap Micro 5.2 | All versions | 3.13.0-150000.4.7.1 |

## How do I fix SUSE-SU-2022:2547-2?

Apply the vendor's patch.

## Is SUSE-SU-2022:2547-2 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2022:2547-2 is a vulnerability in logrotate, published on 25 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:2547-2 in the wild and no public exploit code.

Affected product: logrotate. 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-2547-2/ (Markdown: https://insights.sbomify.com/SUSE-SU-2022-2547-2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2022:2547-2

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