# CVE-2019-3739: Information disclosure in RSA BSAFE Crypto-J

> Attackers can recover ECDSA keys via timing discrepancies in RSA BSAFE Crypto-J, compromising cryptographic security.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Sep 2019
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-p9w8-99j3-73rv

## What is CVE-2019-3739?

CVE-2019-3739 is a medium-severity vulnerability in Oracle Database, published on 18 Sep 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to Information Exposure Through Timing Discrepancy vulnerabilities during ECDSA key generation. A malicious remote attacker could potentially exploit those vulnerabilities to recover ECDSA keys.

Weakness: CWE-203 (Observable Discrepancy), CWE-310

## Which versions are affected by CVE-2019-3739?

It affects 16 products.


Products: Dell Bsafe Cert-J, Dell Bsafe Crypto-J, Dell Bsafe Ssl-J, Oracle Application Performance Management, Oracle Communications Network Integrity, Oracle Database, Oracle Goldengate, Oracle Retail Assortment Planning, Oracle Retail Integration Bus, Oracle Retail Predictive Application Server, Oracle Retail Service Backbone, Oracle Retail Store Inventory Management, Oracle Retail Xstore Point of Service, Oracle Storagetek Acsls, Oracle Storagetek Tape Analytics Sw Tool, Oracle Weblogic Server.

## How do I fix CVE-2019-3739?

No fix has been published for CVE-2019-3739 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-3739 being exploited?

There is no known exploitation of CVE-2019-3739 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Database

- [CVE-2019-3738](https://insights.sbomify.com/CVE-2019-3738/): Weak cryptography in RSA BSAFE Crypto-J (medium 6.5)
- [CVE-2019-3740](https://insights.sbomify.com/CVE-2019-3740/): Information disclosure in RSA BSAFE Crypto-J (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3739 and fix it if it is affected.

What it is: CVE-2019-3739 is a medium-severity vulnerability in Oracle Database, published on 18 Sep 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-3739 in the wild and no public exploit code.

Affected product: Oracle Database. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-3739/ (Markdown: https://insights.sbomify.com/CVE-2019-3739/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-3739
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-3739
- OSV: https://osv.dev/vulnerability/CVE-2019-3739

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-3739/
Summaries are generated and may contain mistakes; the official description above is the record.