Skip to content
Noroxi
CVE-2017-13098· NVD / CVE Program· CNA certcc

BouncyCastle JCE TLS Bleichenbacher/ROBOT

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."

MediumCVSS 5.9 · v3.0—Weaponized Fix available
Published
Dec 12, 2017
Updated
Jun 16, 2026
EPSS
24.3% · 98th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
7 / 30 · 24.3%

CNA vs NVD score

NVD
5.9
CNA · certcc
7.5
1.6 point gap

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
bouncycastlebc-java

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • bouncycastle bc-javabefore 1.59

Versions reported by the vendor

Affected version ranges reported by the assigning authority (certcc). Independent of NVD's CPE analysis and usually ahead of it.

  • Legion of the Bouncy Castle BouncyCastle TLS

    • <1.0.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12bouncycastlebefore 1.58-11.58-1
Debian:9bouncycastlebefore 1.56-1+deb9u11.56-1+deb9u1
Mavenorg.bouncycastle:bcprov-jdk15onbefore 1.0.31.0.3
openSUSE:Leap 15.1bouncycastlebefore 1.60-lp151.3.3.11.60-lp151.3.3.1
openSUSE:Tumbleweedbouncycastlebefore 1.68-3.21.68-3.2

Same product

bouncycastle: all records

Other highest-scoring records for the same primary product.

  • CVE-2007-6721The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as used in Crypto Provider Package before 1.36, has unknown impac
    41Plan
  • CVE-2018-1000613Legion of the Bouncy Castle Legion of the Bouncy Castle Java Cryptography APIs 1.58 up to but not including 1.60 contains a CWE-470: Use of
    40Plan
  • CVE-2026-58062Stapled OCSP response accepted without binding to the checked certificate
    37Monitor
  • CVE-2026-8763Name Constraints bypass via trailing dot in rfc822Name and URI
    37Monitor
  • CVE-2026-59650MTI/A0 DH agreement exponentiates unvalidated peer value
    37Monitor
  • CVE-2026-59638JSSE hostname verifier CN-fallback enabled by default despite documented opt-in
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:bouncycastle1.58-1 · Debian:12Package registry (OSV)
Maven:org.bouncycastle:bcprov-jdk15on1.0.3Package registry (OSV)
opensuse:bouncycastle1.60-lp151.3.3.1 · openSUSE:Leap 15.1Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Metasploit moduleauxiliary/scanner/ssl/bleichenbacher_oracleScanner for Bleichenbacher Oracle in RSA PKCS #1 v1.5auxiliary2009-06-17

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Metasploit-3101 d
  2. Published
  3. TodayOct 10, 2026+3224 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-203 · Observable Discrepancy

CVSS vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records