Sign inStart freeBook a demo

Bouncycastle vulnerabilitiesNone on the known-exploited list.

Vendor
The short answer

Bouncycastle has 25 published vulnerabilities across 13 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Bc-Java, with 19. If you run Bouncycastle software, patch the exploited flaws first.

See the exploited flaws

We keep watching the known-exploited list.

Products

Which Bouncycastle products have the most vulnerabilities?

Bc-Java leads with 19 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.

  1. Bc-Java19
  2. Fips Java API5
  3. Legion-of-the-Bouncy-Castle-Fips-Java-API2
  4. Bouncy Castle Fips .net API1
  5. Bouncy Castle for Java1
  6. Legion-of-the-Bouncy-Castle1
  7. Legion-of-the-Bouncy-Castle-C#-Cryptography-API1
  8. The Bouncy Castle Crypto Package for Java1
  9. Bouncy-Castle-Crypto-Package1
  10. Bouncy Castle Crypto Package1
Published vulnerabilities
Known exploited

Which Bouncycastle vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Bouncycastle's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Bouncycastle flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 24%
    CVE-2017-13098High

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

    CVSS7.5Published13 Dec 2017
  2. 9.1%
    CVE-2019-17359High

    The ASN.1 parser in Bouncy Castle Crypto (aka BC Java) 1.63 can trigger a large attempted memory allocation, and resultant OutOfMemoryError error, via crafted ASN.1 data.

    CVSS7.5Published8 Oct 2019
  3. 7.2%
    CVE-2020-28052High

    An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66.

    CVSS8.1Published18 Dec 2020
  4. 4.8%
    CVE-2015-7940Medium

    The Bouncy Castle Java library before 1.51 does not validate a point is withing the elliptic curve, which makes it easier for remote attackers to obtain private keys via a series of crafted elliptic curve Diffie...

    CVSS5.0Published9 Nov 2015
  5. 4.8%
    CVE-2018-1000613Critical

    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')...

    CVSS9.8Published9 Jul 2018
  6. 3.4%
    CVE-2018-1000180High

    Bouncy Castle BC 1.54 - 1.59, BC-FJA 1.0.0, BC-FJA 1.0.1 and earlier have a flaw in the Low-level interface to RSA key pair generator, specifically RSA Key Pairs generated in low-level API with added certainty may...

    CVSS7.5Published5 Jun 2018
  7. 3.3%
    CVE-2016-1000343High

    In the Bouncy Castle JCE Provider version 1.55 and earlier the DSA key pair generator generates a weak private key if used with default values.

    CVSS7.5Published4 Jun 2018
  8. 3.0%
    CVE-2013-1624Medium

    The TLS implementation in the Bouncy Castle Java library before 1.48 and C# library before 1.8 does not properly consider timing side-channel attacks on a noncompliant MAC check operation during the processing of...

    CVSS4.0Published8 Feb 2013
  9. 2.7%
    CVE-2016-1000339Medium

    In the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine class used for AES was AESFastEngine.

    CVSS5.3Published4 Jun 2018
  10. 2.6%
    CVE-2016-1000341Medium

    In the Bouncy Castle JCE Provider version 1.55 and earlier DSA signature generation is vulnerable to timing attack.

    CVSS5.9Published4 Jun 2018
Every product

All Bouncycastle products we track.

11 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.

This directory lists the 11 Bouncycastle products with at least one tracked version, of 13 in our catalogue.

Precursor Intelligence

Running Bouncycastle? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

Our catalogue lists 25 published vulnerabilities across 13 products and 337 versions from Bouncycastle.

None of Bouncycastle's vulnerabilities is on the list of flaws known to be exploited today.

Bc-Java, with 19 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a Precursor Intelligence account and track the Bouncycastle products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.

Keep exploring