# CVE-2019-1563: Padding Oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey

> An attacker can decrypt RSA-encrypted messages or recover keys via a padding oracle attack if decryption success/failure is observable.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Sep 2019
- **Updated:** 8 Oct 2026
- **Also known as:** ALPINE-CVE-2019-1563, CLEANSTART-2026-RI18304, CLSA-2025-1751271968, DEBIAN-CVE-2019-1563, GHSA-rv3r-f48w-6vvh, JLSEC-2026-218, SUSE-SU-2019:14249-1, UBUNTU-CVE-2019-1563

## What is CVE-2019-1563?

CVE-2019-1563 is a low-severity vulnerability in Openssl Openssl, published on 10 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm), CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2019-1563?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openssl` | SUSE:Linux Enterprise Point of Sale 11 SP3 | All versions | 0.9.8j-0.106.28.1 |
| `openssl` | SUSE:Linux Enterprise Server 11 SP4-LTSS | All versions | 0.9.8j-0.106.28.1 |

Products: Openssl Openssl.

## How do I fix CVE-2019-1563?

Upgrade to a fixed version.

## Is CVE-2019-1563 being exploited?

There is no known exploitation of CVE-2019-1563 in the wild and no public exploit code.

## Other vulnerabilities in Openssl Openssl

- [CVE-2009-3245](https://insights.sbomify.com/CVE-2009-3245/): Null dereference in n/a (critical 10.0)
- [CVE-2006-3738](https://insights.sbomify.com/CVE-2006-3738/): Memory corruption in n/a (critical 10.0)
- [CVE-2026-63073](https://insights.sbomify.com/CVE-2026-63073/): Untrusted Sender DN Used as Format String in CMP Response Validation (critical 9.8)
- [CVE-2016-6309](https://insights.sbomify.com/CVE-2016-6309/): Use after free in n/a (critical 9.8)
- [CVE-2016-0799](https://insights.sbomify.com/CVE-2016-0799/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1563 and fix it if it is affected.

What it is: CVE-2019-1563 is a low-severity vulnerability in Openssl Openssl, published on 10 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1563 in the wild and no public exploit code.

Affected product: Openssl 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/CVE-2019-1563/ (Markdown: https://insights.sbomify.com/CVE-2019-1563/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1563
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1563
- OSV: https://osv.dev/vulnerability/CVE-2019-1563

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