Skip to content
Fencer Intel
critical 9.8

CVE-2018-1000613 json

Deserialization of Untrusted Data in Bouncy castle

published 8y ago modified 4mo ago also GHSA-4446-656p-f54g , EUVD-2018-0492

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.8%
EPSS 4.8% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.bouncycastle:bcprov-jdk15on 1.60
  • bouncycastle bc-java 1.60
  • oracle communications_converged_application_server 7.0.0.1
  • oracle communications_webrtc_session_controller 7.2
  • bouncycastle Debian 14, Debian 13, Debian 12 1.60-1

debian advisories DEBIAN-CVE-2018-1000613

  • bouncycastle openSUSE Tumbleweed 1.68-3.2
  • bouncycastle openSUSE Leap 15.1 1.60-lp151.3.3.1

opensuse advisories openSUSE-SU-2024:10661-1openSUSE-SU-2020:0607-1

Is CVE-2018-1000613 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1000613 updated cvss 4.9

bouncycastle: lack of class checking in deserialization of XMSS/XMSS^MT private keys with BDS state information

  • Red Hat JBoss Data Virtualization 6 bouncycastle bouncycastle
    affected: no fix planned “Will not fix”
  • Red Hat JBoss Developer Studio 11 bouncycastle bouncycastle Red Hat Fuse 7 jclouds-bouncycastle jclouds-bouncycastle Red Hat JBoss Enterprise Application Platform 7 bouncycastle bouncycastle Red Hat JBoss Fuse 6 jclouds-bouncycastle jclouds-bouncycastle Red Hat Satellite 6 bouncycastle Red Hat Software Collections rh-eclipse46-bouncycastle, rh-eclipse46-bouncycastle-javadoc
    +2 more products
    Red Hat Subscription Asset Manager bouncycastle Red Hat Virtualization 4 eap7-bouncycastle
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
2y ago

Exploit prediction

4.77% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.bouncycastle:bcprov-jdk15on
>=1.57, <1.60
1.60

Classification

Weakness
  • CWE-470 Use of Externally-Controlled Input to Select Classes or Code
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.