# openSUSE-SU-2020:0631-1: Security update for rpmlint

> This update for rpmlint whitelists certmonger to resolve specific issues, requiring no specific attack vector or impact description.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2020

## What is openSUSE-SU-2020:0631-1?

openSUSE-SU-2020:0631-1 is a vulnerability in rpmlint, published on 8 May 2020. 

### Official description

This update for rpmlint fixes the following issues:

- whitelist certmonger (bsc#1169365, bsc#1129452)

This update was imported from the SUSE:SLE-15:Update update project.

## Which versions are affected by openSUSE-SU-2020:0631-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rpmlint` | openSUSE:Leap 15.1 | All versions | 1.10-lp151.9.6.1 |
| `rpmlint-mini` | openSUSE:Leap 15.1 | All versions | 1.10-lp151.5.13.1 |
| `rpmlint-tests` | openSUSE:Leap 15.1 | All versions | 84.87+git20181018.60e0249-lp151.9.6.1 |

## How do I fix openSUSE-SU-2020:0631-1?

Apply the vendor's patch.

## Is openSUSE-SU-2020:0631-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2020:0631-1 is a vulnerability in rpmlint, published on 8 May 2020. 
Exploitation: There is no known exploitation of openSUSE-SU-2020:0631-1 in the wild and no public exploit code.

Affected product: rpmlint. 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/openSUSE-SU-2020-0631-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2020-0631-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2020:0631-1

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