Security readout for executives and security teams
Plain-English summary
CVE-2019-3740 affects RSA BSAFE Crypto-J before 6.2.5. A timing weakness during DSA key generation could let a remote attacker recover DSA private keys in some circumstances. The risk is mainly confidentiality of cryptographic keys, not service availability or data modification.
Executive priority
Treat this as a targeted cryptographic confidentiality risk. Prioritize environments that generate or manage DSA keys with affected Crypto-J versions, especially in externally reachable workflows. It is not KEV-listed in the provided data, so urgency is lower than actively exploited vulnerabilities.
Technical view
The issue is an information exposure through timing discrepancy in DSA key generation in RSA BSAFE Crypto-J prior to 6.2.5. CVSS 3.0 is 6.5 with network attack vector, low complexity, no privileges, required user interaction, and high confidentiality impact.
Likely exposure
Exposure is most likely where applications directly use RSA BSAFE Crypto-J before 6.2.5 or include it as an embedded dependency. Oracle CPU pages are listed as references, but the provided bundle does not enumerate specific downstream Oracle products affected by this CVE.
Exploitation context
The bundle says a malicious remote attacker could potentially recover DSA keys. It does not cite active exploitation, CISA KEV listing, exploit availability, or practical attack details. User interaction is present in the CVSS vector, but the bundle does not explain that interaction.
Researcher notes
Key unknowns are downstream product mapping, attack preconditions beyond CVSS user interaction, and whether generated keys remain exposed after creation. The Dell advisory is the primary remediation reference in the bundle; Oracle CPU links indicate vendor tracking but require product-specific interpretation.
Mitigation direction
- Upgrade RSA BSAFE Crypto-J to 6.2.5 or later.
- Review Dell advisory DSA-2019-094 for vendor remediation details.
- Check Oracle CPU references for downstream product patch status.
- Inventory applications that bundle or depend on Crypto-J.
- Assess DSA key rotation needs under vendor guidance.
Validation and detection
- Identify deployed RSA BSAFE Crypto-J versions.
- Confirm no runtime or packaged dependency is earlier than 6.2.5.
- Review SBOMs and vendor notices for embedded Crypto-J usage.
- Check whether DSA key generation occurs in affected applications.
- Verify applicable Dell or Oracle fixes are installed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-310: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-3740 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
6.5MediumVector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.oracle.com/security-alerts/cpujul2020.htmlCVE reference · x_refsource_MISC
- https://www.dell.com/support/security/en-us/details/DOC-106556/DSA-2019-094-RSA-BSAFE®%3B-Crypto-J-Multiple-Security-VulnerabilitiesCVE reference · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpuoct2020.htmlCVE reference · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpuApr2021.htmlCVE reference · x_refsource_MISC
- https://www.oracle.com//security-alerts/cpujul2021.htmlCVE reference · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpuoct2021.htmlCVE reference · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpuapr2022.htmlCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cryptographic Issues
Cryptographic Issues represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.