Bc-Java vulnerabilitiesRanked by how likely they are to be used.
Bc-Java is made by Bouncycastle. We track 19 published vulnerabilities in it, across 83 versions. None of them is on the list of flaws known to be exploited today. If you run Bc-Java, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Bc-Java vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Bc-Java's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Bc-Java 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.
- 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...
- 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.
- 7.2%CVE-2020-28052High
An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66.
- 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')...
- 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...
- 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.
- 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...
- 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.
- 2.6%CVE-2016-1000345Medium
In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding oracle attack.
- 2.6%CVE-2016-1000341Medium
In the Bouncy Castle JCE Provider version 1.55 and earlier DSA signature generation is vulnerable to timing attack.
Running Bc-Java? 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.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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."
- Matched to
- Bc-Java on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 19 published vulnerabilities listed under the name Bc-Java, across 83 versions.
None of Bc-Java's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Bc-Java. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.