Vulnerability · CVE-2019-3738
RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to a Missing Required Cryptographic Step vulnerability.
Published Sep 18, 2019 · corrected/updated Jun 17, 2026 · Oracle bsafe cert-j · evidence confidence high
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 vulnerability to coerce two parties into computing the same predictable shared key.
Grounded briefings
Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.
Executive
CVE-2019-3738 is a medium public vulnerability record for Oracle bsafe cert-j. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.
System administrator
Identify whether Oracle bsafe cert-j is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: dell/bsafe cert-j; dell/bsafe crypto-j; dell/bsafe ssl-j; mcafee/threat intelligence exchange server. Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.
Security analyst
Signals on file: CVSS 6.5. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-325, CWE-347. Sources contributing to this record: cve_org, oracle. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.
Exploitation and remediation
Exploitation evidence
Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.
Patch and remediation
No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Sep 18, 2019 · Oracle Critical Patch Updates
Detected
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 vulnerability to coerce two parties into computing the same predictable shared key.
Jun 17, 2026 · Oracle Critical Patch Updates
Updated
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 vulnerability to coerce two parties into computing the same predictable shared key.
Affected
- cpe dell/bsafe cert-jversion unspecified
- cpe dell/bsafe crypto-jversion unspecified
- cpe dell/bsafe ssl-jversion unspecified
- cpe mcafee/threat intelligence exchange serverversion unspecified
- cpe mcafee/threat intelligence exchange server3.0.0
- cpe oracle/application performance management13.3.0.0
- cpe oracle/application performance management13.4.0.0
- cpe oracle/communications network integrity7.3.2
- cpe oracle/communications network integrity7.3.5
- cpe oracle/communications network integrity7.3.6
- cpe oracle/communications unified inventory management7.3.2
- cpe oracle/communications unified inventory management7.3.4
Sources
- CVE.orgVulnerability recordCVE-2019-3738
Official CVE identifier
cve.org - Oracle Critical Patch UpdatesVendor advisoryCVE-2019-3738
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 vulnerability to coerce two parties into computing the same predictable shared key.
nvd.nist.gov