# CVE-2017-13098: BouncyCastle JCE TLS Bleichenbacher/ROBOT

> Attackers can recover private keys from applications using BouncyCastle TLS with JCE and RSA key exchange via a Bleichenbacher oracle.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 13 Dec 2017
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2017-13098, DSA-4072-1, GHSA-wrwf-pmmj-w989

## What is CVE-2017-13098?

CVE-2017-13098 is a high-severity vulnerability in Bouncycastle Bc-Java, published on 13 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BouncyCastle TLS prior to version 1.0.3, when configured to use the JCE (Java Cryptography Extension) for cryptographic functions, provides a weak Bleichenbacher oracle when any TLS cipher suite using RSA key exchange is negotiated. An attacker can recover the private key from a vulnerable application. This vulnerability is referred to as "ROBOT."

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2017-13098?

2 open source packages ship an affected version, including org.bouncycastle:bcprov-jdk15on. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.bouncycastle:bcprov-jdk15on` | Maven | All versions | 1.0.3 |
| `org.bouncycastle:bcprov-jdk15on` | Maven | All versions | 1.0.3 |

Products: Bouncycastle Bc-Java.

## How do I fix CVE-2017-13098?

Upgrade org.bouncycastle:bcprov-jdk15on to 1.0.3 or later.

## Is CVE-2017-13098 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-13098 exists.

Public exploit code:

- Scanner for Bleichenbacher Oracle in RSA PKCS #1 v1.5 (metasploit)

## Other vulnerabilities in Bouncycastle Bc-Java

- [CVE-2007-6721](https://insights.sbomify.com/CVE-2007-6721/): Legion of the Bouncy Castle Java Cryptography API Bleichenbacher Oracle Vulnerability (critical 10.0)
- [CVE-2018-1000613](https://insights.sbomify.com/CVE-2018-1000613/): Deserialization of Untrusted Data in Bouncy castle (critical 9.8)
- [CVE-2026-58062](https://insights.sbomify.com/CVE-2026-58062/): Stapled OCSP response accepted without binding to the checked certificate (critical 9.3)
- [CVE-2026-59638](https://insights.sbomify.com/CVE-2026-59638/): JSSE hostname verifier CN-fallback enabled by default despite documented opt-in (critical 9.3)
- [CVE-2026-59650](https://insights.sbomify.com/CVE-2026-59650/): MTI/A0 DH agreement exponentiates unvalidated peer value (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-13098 and fix it if it is affected.

What it is: CVE-2017-13098 is a high-severity vulnerability in Bouncycastle Bc-Java, published on 13 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-13098 exists.

Affected packages and fixed versions:
- org.bouncycastle:bcprov-jdk15on (Maven): affected all versions; fixed in 1.0.3
- org.bouncycastle:bcprov-jdk15on (Maven): affected all versions; fixed in 1.0.3

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-2017-13098/ (Markdown: https://insights.sbomify.com/CVE-2017-13098/index.md)
```

## Sources

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

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