Bsafe Crypto J
Vendor:
First CVE: Oct 11, 2013 · Active for 12 years
10
Total CVEs
More Total CVEs than 89% of tracked products
1.4
Avg CVEs / Year
Higher CVE frequency than 59% of tracked products
6.6
Avg CVSS
Higher Avg CVSS than 36% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Bsafe Crypto J over time
Volume of CVEsAvg CVSS Base Score
First CVE
Oct 11, 2013
12 years ago
Most Recent CVE
Sep 25, 2025
306 days ago
CVE Severity & Scoring
Bsafe Crypto J10 CVEs
10%
60%
20%
10%
All CVEs353,173 CVEs
45%
40%
11%
LowMediumHighCritical
Attack Vector
Local0 (0.0%)
Network9 (90.0%)
Unknown1 (10.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low6 (60.0%)
High3 (30.0%)
Unknown1 (10.0%)
User Interaction
None6 (60.0%)
Unknown1 (10.0%)
Required3 (30.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None9 (90.0%)
Unknown1 (10.0%)
Top CVEs
Signals from CVEs in this product scope (10 CVEs).
10 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
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. An unaut | Feb 2, 2024 | 9.8 | 28 | NO | NO |
CVE-2025-26333HIGH Dell BSAFE Crypto-J generates an error message that includes sensitive information about its environment and associated data. A remote attacker could potentially exploit this vulne | Sep 25, 2025 | 7.5 | 25 | NO | NO |
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. A malicious remote attack | Sep 18, 2019 | 6.5 | 24 | NO | NO |
CVE-2016-8212HIGH An issue was discovered in EMC RSA BSAFE Crypto-J versions prior to 6.2.2. There is an Improper OCSP Validation Vulnerability. OCSP responses have two time values: thisUpdate and n | Feb 3, 2017 | 7.5 | 24 | NO | NO |
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. A malicious remote attacke | Sep 18, 2019 | 6.5 | 22 | NO | NO |
CVE-2019-3738MEDIUM RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to a Missing Required Cryptographic Step vulnerability. A malicious remote attacker could potentially exploit this vulnera | Sep 18, 2019 | 6.5 | 22 | NO | NO |
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 | Sep 11, 2018 | 5.9 | 21 | NO | NO |
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 relationshi | Oct 11, 2013 | 5.8 | 21 | NO | NO |
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 BSA | Apr 12, 2016 | 5.9 | 20 | NO | NO |
EMC RSA BSAFE Crypto-J versions prior to 6.2.2 has a PKCS#12 Timing Attack Vulnerability. A possible timing attack could be carried out by modifying a PKCS#12 file that has an inte | Feb 3, 2017 | 3.7 | 15 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (10 CVEs).
CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%
Social Chatter
Signals from CVEs in this product scope (10 CVEs).
Media Mentions
Signals from CVEs in this product scope (10 CVEs).
Top CNAs Publishing CVEs For Bsafe Crypto J
Top CWEs
Versions
| Version | CVE Count | Avg CVSS | Avg EPSS | KEV | Exploits |
|---|---|---|---|---|---|
| 7.0 | 1 | 7.5 | 0.3% | 0 | 0 |
| 5.0.1 | 1 | 5.8 | 1.6% | 0 | 0 |
| 5.0 | 1 | 5.8 | 1.6% | 0 | 0 |