# SUSE-SU-2022:2824-1: Security update for compat-openssl098

> Fixes a regression in the compat-openssl098 library caused by unknown options passed to the openssl x509 command from c_rehash.

- **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:** 16 Aug 2022

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

SUSE-SU-2022:2824-1 is a vulnerability in compat-openssl098, published on 16 Aug 2022. 

### Official description

This update for compat-openssl098 fixes the following issues:

- Fixed a regression caused by unknown option passed to 'openssl x509' from c_rehash

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `compat-openssl098` | SUSE:Linux Enterprise Module for Legacy 12 | All versions | 0.9.8j-106.39.1 |
| `compat-openssl098` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 0.9.8j-106.39.1 |
| `compat-openssl098` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 0.9.8j-106.39.1 |

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2022:2824-1 is a vulnerability in compat-openssl098, published on 16 Aug 2022. 
Exploitation: There is no known exploitation of SUSE-SU-2022:2824-1 in the wild and no public exploit code.

Affected product: compat-openssl098. 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-2824-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2022-2824-1/index.md)
```

## Sources

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

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