# SUSE-SU-2019:1141-1: Security update for openssl-1_1


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 May 2019

## What is SUSE-SU-2019:1141-1?

SUSE-SU-2019:1141-1 is a vulnerability in openssl-1_1, published on 3 May 2019. 

### Official description

This update for openssl-1_1 to version 1.1.1b fixes the following issues:

- Changed the info callback signals for the start and end of a post-handshake
  message exchange in TLSv1.3.
- Fixed a bug in DTLS over SCTP. This breaks interoperability with older versions
  of OpenSSL like OpenSSL 1.1.0 and OpenSSL 1.0.2.
- Fixed the handling of strerror_r with glibc.

## Which versions are affected by SUSE-SU-2019:1141-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openssl-1_1` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 1.1.1b-2.12.2 |
| `openssl-1_1` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 1.1.1b-2.12.2 |
| `openssl-1_1` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 1.1.1b-2.12.2 |
| `openssl-1_1` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 1.1.1b-2.12.2 |

## How do I fix SUSE-SU-2019:1141-1?

Upgrade to a fixed version.

## Is SUSE-SU-2019:1141-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2019:1141-1 is a vulnerability in openssl-1_1, published on 3 May 2019. 
Exploitation: There is no known exploitation of SUSE-SU-2019:1141-1 in the wild and no public exploit code.

Affected product: openssl-1_1. 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-2019-1141-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2019-1141-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2019:1141-1

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