CVE-2019-3740: RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to an Information Exposure Through Timing Discrepancy vulnerabilities during DSA…
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.8% (FIRST EPSS); higher than 90.4% of all records.
- 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.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Oct 8, 2026
- EPSS
- 3.8% · 90th percentile
- CWE
- CWE-310
Report tools
Action score
27
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| 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
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
Affected versions · NVD (20)
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
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…27Monitor
- 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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0331 · Apr 21, 2021(Oracle Güvenlik Uyarısı Yayınladı)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (1)
- SSVC exploitation— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.