# SUSE-SU-2020:0516-1: Security update for openssl

> An attacker can exploit a Bleichenbacher attack to decrypt TLS traffic or cause memory leaks in OpenSSL, requiring a security patch.

- **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:** 27 Feb 2020

## What is SUSE-SU-2020:0516-1?

SUSE-SU-2020:0516-1 is a vulnerability in openssl, published on 27 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for openssl fixes the following issues:

- Add missing commits fixing the security issue called 'The 9 Lives of Bleichenbacher's CAT'. (bsc#1117951)
- Fix a memory leak problem in function 'BN_copy()'. (bsc#1160163)

## Which versions are affected by SUSE-SU-2020:0516-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openssl` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 1.0.1i-54.32.1 |
| `openssl` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.0.1i-54.32.1 |

## How do I fix SUSE-SU-2020:0516-1?

Apply the vendor's patch.

## Is SUSE-SU-2020:0516-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2020:0516-1 is a vulnerability in openssl, published on 27 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2020:0516-1 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2020:0516-1

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