dbcve.org
Bc JavaApplication · Bouncycastle

CVE-2018-1000613

CRITICAL · 9.8 CVSS v3.1 Published 2018-07-09
Fix available
A fix is available. Upgrade to 1.60 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Legion 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 Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in XMSS/XMSS^MT private key deserialization that can result in Deserializing an XMSS/XMSS^MT private key can result in the execution of unexpected code. This attack appear to be exploitable via A handcrafted private key can include references to unexpected classes which will be picked up from the class path for the executing application. This vulnerability appears to have been fixed in 1.60 and later.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Bc JavaApplication
Affected:>= 1.58, < 1.60
Oncommand Workflow AutomationApplication
Affected:all versions
LeapOperating system
Affected:= 15.1
Api GatewayApplication
Affected:= 11.1.2.4.0
Banking PlatformApplication
Affected:= 2.6.0= 2.6.1= 2.6.2
Business Process Management SuiteApplication
Affected:= 11.1.1.9.0= 12.1.3.0.0= 12.2.1.3.0
Business Transaction ManagementApplication
Affected:= 12.1.0
Communications Application Session ControllerApplication
Affected:= 3.7.1= 3.8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.60 or later
Fixed in 1.60
Vendor patch github.com →
Recommended fix High confidence

Bouncy Castle Java 1.60 or later (recommended: 1.70 or latest stable)

  1. Identify all Java applications and dependencies that include the Bouncy Castle (bc) library
  2. Check current Bouncy Castle version in use (examine pom.xml, build.gradle, dependencies, or JAR manifest files)
  3. For Maven-based projects: update the dependency in pom.xml to version 1.60 or later (e.g., <version>1.70</version>)
  4. For Gradle-based projects: update the dependency to implementation 'org.bouncycastle:bcprov-jdk15on:1.70'
  5. Rebuild the application and run tests to verify functionality after the upgrade
  6. Redeploy the updated application to production environments
  7. For products listed as affected (Oncommand Workflow Automation, Leap, Api Gateway, etc.), apply vendor-supplied patches that update the bundled Bouncy Castle library to version 1.60 or later
Caveat Minimal risk for most applications; verify any custom cryptographic code that directly uses the XMSS/XMSS^MT key classes

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1000613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1000613 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data