Security readout for executives and security teams
Plain-English summary
This flaw affects RSA BSAFE Crypto-J before 6.2.5. Timing differences during ECDSA key generation could leak enough information for a remote attacker to potentially recover ECDSA keys. The business concern is confidentiality of cryptographic keys, not service outage.
Executive priority
Treat as a focused cryptographic confidentiality risk. Prioritize systems that generate or protect important ECDSA keys, especially externally reachable services or products with embedded BSAFE Crypto-J.
Technical view
CVE-2019-3739 is a timing side-channel issue in ECDSA key generation in RSA BSAFE Crypto-J prior to 6.2.5. CVSS 3.0 is 6.5 with network attack vector, no privileges, user interaction required, and high confidentiality impact.
Likely exposure
Exposure is likely where applications, middleware, or bundled products use RSA BSAFE Crypto-J versions before 6.2.5 and perform ECDSA key generation. The bundle does not identify every downstream product or deployment pattern.
Exploitation context
The sources describe potential remote exploitation with user interaction, but do not cite active exploitation. The CVE is not listed as KEV in the provided bundle. No exploit maturity or public exploitation evidence is provided.
Researcher notes
Evidence supports a timing discrepancy during ECDSA key generation with potential key recovery. The bundle lacks detailed proof-of-concept information, affected downstream product mapping, and operational indicators. Avoid assuming exploitation beyond the stated potential impact.
Mitigation direction
- Inventory uses of RSA BSAFE Crypto-J across applications and vendor products.
- Upgrade RSA BSAFE Crypto-J to 6.2.5 or later where applicable.
- Review Dell advisory guidance for supported remediation details.
- Check Oracle CPU references for downstream product applicability.
- Rotate potentially exposed ECDSA keys if vulnerable key generation occurred.
Validation and detection
- Confirm deployed RSA BSAFE Crypto-J versions are 6.2.5 or later.
- Identify systems that generated ECDSA keys using vulnerable versions.
- Check software composition records for embedded BSAFE Crypto-J dependencies.
- Review vendor advisories for product-specific exposure and fixes.
- Verify no vulnerable library versions remain in production artifacts.
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-3739 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.