# openSUSE-SU-2022:0095-1: Security update for openSUSE-build-key

> An update disables a weak 1024-bit RSA build key for the end-of-life SLE11 distribution to prevent potential trust issues.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2022

## What is openSUSE-SU-2022:0095-1?

openSUSE-SU-2022:0095-1 is a vulnerability in openSUSE-build-key, published on 30 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for openSUSE-build-key fixes the following issues:

- Disabled the SLE11 build key as SLE11 is EOL now, also key was
  1024bit RSA (removed gpg-pubkey-307e3d54-5aaa90a5.asc)
  Also obsolete old build key.

## Which versions are affected by openSUSE-SU-2022:0095-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openSUSE-build-key` | openSUSE:Leap 15.3 | All versions | 1.0-lp153.4.8.1 |

## How do I fix openSUSE-SU-2022:0095-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2022:0095-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2022:0095-1 is a vulnerability in openSUSE-build-key, published on 30 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of openSUSE-SU-2022:0095-1 in the wild and no public exploit code.

Affected product: openSUSE-build-key. 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-2022-0095-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2022-0095-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2022:0095-1

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