RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to an Information Exposure Through Timing Discrepancy vulnerabilities during DSA k
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.
- Published
- Sep 18, 2019
- Updated
- Jun 16, 2026
- EPSS
- 3.8% · 90th percentile
- CWE
- CWE-310
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.8%
CNA vs NVD score
- NVD
- 6.5
- CNA · dell
- 6.5
- agree
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| dell | bsafe cert-j | cpe:2.3:a:dell:bsafe_cert-j |
| dell | bsafe crypto-j | cpe:2.3:a:dell:bsafe_crypto-j |
| dell | bsafe ssl-j | cpe:2.3:a:dell:bsafe_ssl-j |
| oracle | application performance management | cpe:2.3:a:oracle:application_performance_management |
| oracle | communications network integrity | cpe:2.3:a:oracle:communications_network_integrity |
| oracle | communications unified inventory management | cpe:2.3:a:oracle:communications_unified_inventory_management |
| oracle | database | cpe:2.3:a:oracle:database |
| oracle | global lifecycle management opatch | cpe:2.3:a:oracle:global_lifecycle_management_opatch |
| oracle | goldengate | cpe:2.3:a:oracle:goldengate |
| oracle | retail assortment planning | cpe:2.3:a:oracle:retail_assortment_planning |
| oracle | retail integration bus | cpe:2.3:a:oracle:retail_integration_bus |
| oracle | retail predictive application server | cpe:2.3:a:oracle:retail_predictive_application_server |
and 6 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dell bsafe cert-jup to 6.2.4 inclusive
- dell bsafe crypto-jbefore 6.2.5
- dell bsafe ssl-jup to 6.2.4.1 inclusive
- oracle application performance management13.3.0.0
- oracle application performance management13.4.0.0
- oracle communications network integrity7.3.2
- oracle communications network integrity7.3.5
- oracle communications network integrity7.3.6
- oracle communications unified inventory management7.3.2
- oracle communications unified inventory management7.3.4
- oracle communications unified inventory management7.3.5
- oracle communications unified inventory management7.4.0
- oracle communications unified inventory management7.4.1
- oracle database12.1.0.2
- oracle database12.2.0.1
- oracle database18c
- oracle database19c
- oracle global lifecycle management opatchbefore 12.2.0.1.22
- oracle goldengatebefore 19.1.0.0.0.210420
- oracle retail assortment planning15.0.3.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (dell). Independent of NVD's CPE analysis and usually ahead of it.
Dell RSA BSAFE Crypto-J
- prior to 6.2.5affected
Same product
dell: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-3739RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to Information Exposure Through Timing Discrepancy vulnerabilities during ECDSA ke27Monitor
- CVE-2019-3738RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to a Missing Required Cryptographic Step vulnerability.27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-310 · Cryptographic IssuesCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- www.dell.com/support/security/en-us/details/DOC-106556/DSA-2019-094-RSA-BSAFE®%3B-Crypto-J-Multiple-Security-Vulnerabilities
- www.oracle.com//security-alerts/cpujul2021.html
- www.oracle.com/security-alerts/cpuApr2021.html
- www.oracle.com/security-alerts/cpuapr2022.html
- www.oracle.com/security-alerts/cpujul2020.html
- www.oracle.com/security-alerts/cpuoct2020.html
- www.oracle.com/security-alerts/cpuoct2021.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.