{"answers":{"affected":"It affects 16 products.","exploited":"There is no known exploitation of CVE-2019-3739 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-3739 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2019-3739 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2019-3739 in the wild and no public exploit code.\n\nAffected product: Oracle Database. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-3739/ (Markdown: https://insights.sbomify.com/CVE-2019-3739/index.md)","id":"CVE-2019-3739","markdown":"https://insights.sbomify.com/CVE-2019-3739/index.md","name":"CVE-2019-3739","record":{"aliases":["GHSA-p9w8-99j3-73rv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Java cryptographic library","requires_auth":"none","summary":"Attackers can recover ECDSA keys via timing discrepancies in RSA BSAFE Crypto-J, compromising cryptographic security.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"bsafe_cert-j","vendor":"dell"},{"product":"bsafe_crypto-j","vendor":"dell"},{"product":"bsafe_ssl-j","vendor":"dell"},{"product":"application_performance_management","vendor":"oracle"},{"product":"communications_network_integrity","vendor":"oracle"},{"product":"database","vendor":"oracle"},{"product":"goldengate","vendor":"oracle"},{"product":"retail_assortment_planning","vendor":"oracle"},{"product":"retail_integration_bus","vendor":"oracle"},{"product":"retail_predictive_application_server","vendor":"oracle"},{"product":"retail_service_backbone","vendor":"oracle"},{"product":"retail_store_inventory_management","vendor":"oracle"},{"product":"retail_xstore_point_of_service","vendor":"oracle"},{"product":"storagetek_acsls","vendor":"oracle"},{"product":"storagetek_tape_analytics_sw_tool","vendor":"oracle"},{"product":"weblogic_server","vendor":"oracle"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"},{"id":"CWE-310","name":null}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in RSA BSAFE Crypto-J","id":"CVE-2019-3739","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"oracle:database","products":["oracle:database","oracle:retail_xstore_point_of_service","oracle:weblogic_server"],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":7,"next":{"headline":"Information disclosure in RSA BSAFE Crypto-J","id":"CVE-2019-3740"},"packages":[],"prev":{"headline":"Weak cryptography in RSA BSAFE Crypto-J","id":"CVE-2019-3738"},"products":["RSA BSAFE Crypto-J"],"published":"2019-09-18","related":[{"cvss_score":6.5,"headline":"Weak cryptography in RSA BSAFE Crypto-J","id":"CVE-2019-3738","kev_date_added":null,"published":"2019-09-18"},{"cvss_score":6.5,"headline":"Information disclosure in RSA BSAFE Crypto-J","id":"CVE-2019-3740","kev_date_added":null,"published":"2019-09-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["Dell"]},"summary":"Attackers can recover ECDSA keys via timing discrepancies in RSA BSAFE Crypto-J, compromising cryptographic security.","url":"https://insights.sbomify.com/CVE-2019-3739/"}