Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 24.28% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2017
CVE-2017-13098High confidence
BouncyCastle JCE TLS Bleichenbacher/ROBOT
Legion of the Bouncy Castle · BouncyCastle TLS
7.5HighCVSS 3.0
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 22 Oct 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Legion of the Bouncy Castle BouncyCastle TLS and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
4 package statesRelease-specific package status
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | bouncycastle | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.58-1 | Debian Security Tracker ↗Source updated 22 Oct 2026 |
| Debian bookwormbookworm · source | bouncycastle | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.58-1 | Debian Security Tracker ↗Source updated 22 Oct 2026 |
| Debian forkyforky · source | bouncycastle | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.58-1 | Debian Security Tracker ↗Source updated 22 Oct 2026 |
| Debian sidsid · source | bouncycastle | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.58-1 | Debian Security Tracker ↗Source updated 22 Oct 2026 |
Direct vendor intelligence
0 current · 1 archivedAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
ARUBA-PSA-2022-004 · CSAF 2.0 · revision 2 · finalHPE Aruba NetworkingReturn Of Bleichenbacher's Oracle ThreatNo longer in the provider’s current catalogue
The vendor explicitly identifies these products as affected by this CVE.
- AOS-CX
- Summary
- A vulnerability exists within AOS-CX's cryptographic library that provides a weak Bleichenbacher oracle when any TLS cipher suite using RSA key exchange is negotiated. An attacker may be able to recover private keys for X.509 certificates. This vulnerability is referred to as "ROBOT."
- Remediation
- The vulnerabilities contained in this advisory can be addressed by patching or upgrading to one of the versions listed below AOS-CX 10.06.xxxx: 10.06.0180 and above AOS-CX 10.07.xxxx: 10.07.0061 and above AOS-CX 10.08.xxxx: 10.08.1040 and above AOS-CX 10.09.xxxx: 10.09.0010 and above Aruba recommends that users using the following branches upgrade to 10.06.0180 and above to address these vulnerabilities: AOS-CX 10.05.xxxx and below None of the above branch versions will address the UEFI vulnerabilities mentioned in ARUBA-PSA-2022-001.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
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."
What
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."
Why
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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."
Why
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Observable Discrepancy → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-203 ↗
CWE-203: Observable Discrepancy. The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCommon Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- BouncyCastle TLS: <1.0.3
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04
Evidence and provenance
Published 13 Dec 2017 · Last source change 16 Sept 2024, 18:39 UTC · CWE-203 · Observable Discrepancy
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-01
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2022-5636
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed from remediation: csaf.arubanetworking.hpe.com/hpe_aruba_networking_-_2022-004.json to advisory no longer present in the provider's current catalogue.HPE Aruba Networking ↗
- Before
- remediation: csaf.arubanetworking.hpe.com/hpe_aruba_networking_-_2022-004.json
- After
- advisory no longer present in the provider's current catalogue
- ENISA EUVD mappingEUVD-2022-5636 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2022-5636"}
- Vendor guidanceAuthoritative vendor guidance changed: added mitigation: kb.cert.org/144389; added patch: github.com/a00b684465b38d722ca9a3543b8af8568e6bad5c; removed vendor advisory: debian.org/dsa-4072; removed vendor advisory: lists.opensuse.org/msg00011.html; 1 further additions.github.com ↗
- Before
- vendor advisory: debian.org/dsa-4072 · vendor advisory: lists.opensuse.org/msg00011.html
- After
- mitigation: kb.cert.org/144389 · patch: github.com/a00b684465b38d722ca9a3543b8af8568e6bad5c · remediation: github.com/a00b684465b38d722ca9a3543b8af8568e6bad5c
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- <1.0.3 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- <1.0.3 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.github.com ↗
- Before
- Awaiting fix
- After
- Patch available
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.