Bsafe Crypto-J vulnerabilitiesRanked by how likely they are to be used.
Bsafe Crypto-J is made by Dell. We track 9 published vulnerabilities in it, across 37 versions. None of them is on the list of flaws known to be exploited today. If you run Bsafe Crypto-J, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Bsafe Crypto-J vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Bsafe Crypto-J's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Bsafe Crypto-J 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.
- 3.9%CVE-2019-3740Medium
RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to an Information Exposure Through Timing Discrepancy vulnerabilities during DSA key generation.
- 3.5%CVE-2016-0887Medium
EMC RSA BSAFE Micro Edition Suite (MES) 4.0.x and 4.1.x before 4.1.5, RSA BSAFE Crypto-C Micro Edition (CCME) 4.0.x and 4.1.x before 4.1.3, RSA BSAFE Crypto-J before 6.2.1, RSA BSAFE SSL-J before 6.2.1, and RSA BSAFE...
- 2.6%CVE-2019-3739Medium
RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to Information Exposure Through Timing Discrepancy vulnerabilities during ECDSA key generation.
- 1.9%CVE-2016-8212High
An issue was discovered in EMC RSA BSAFE Crypto-J versions prior to 6.2.2.
- 1.7%CVE-2019-3738Medium
RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to a Missing Required Cryptographic Step vulnerability.
- 1.7%CVE-2018-11070Medium
RSA BSAFE Crypto-J versions prior to 6.2.4 and RSA BSAFE SSL-J versions prior to 6.2.4 contain a Covert Timing Channel vulnerability during PKCS #1 unpadding operations, also known as a Bleichenbacher attack.
- 1.6%CVE-2007-6755Medium
The NIST SP 800-90A default statement of the Dual Elliptic Curve Deterministic Random Bit Generation (Dual_EC_DRBG) algorithm contains point Q constants with a possible relationship to certain "skeleton key" values,...
- 1.5%
EMC RSA BSAFE Crypto-J versions prior to 6.2.2 has a PKCS#12 Timing Attack Vulnerability.
- 1.0%CVE-2022-34381Critical
Dell BSAFE SSL-J version 7.0 and all versions prior to 6.5, and Dell BSAFE Crypto-J versions prior to 6.2.6.1 contain an unmaintained third-party component vulnerability.
Running Bsafe Crypto-J? 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
RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to an Information Exposure Through Timing Discrepancy vulnerabilities during DSA key generation. A malicious remote attacker could potentially exploit those vulnerabilities to recover DSA keys.
- Matched to
- Bsafe Crypto-J 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 9 published vulnerabilities listed under the name Bsafe Crypto-J, across 37 versions.
None of Bsafe Crypto-J's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Bsafe Crypto-J. 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.