{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-11070 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-11070 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-11070 is a medium-severity vulnerability in Dell EMC RSA BSAFE Crypto-J, published on 11 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-11070 and fix it if it is affected.\n\nWhat it is: CVE-2018-11070 is a medium-severity vulnerability in Dell EMC RSA BSAFE Crypto-J, published on 11 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-11070 in the wild and no public exploit code.\n\nAffected product: Dell EMC RSA BSAFE Crypto-J. 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-2018-11070/ (Markdown: https://insights.sbomify.com/CVE-2018-11070/index.md)","id":"CVE-2018-11070","markdown":"https://insights.sbomify.com/CVE-2018-11070/index.md","name":"CVE-2018-11070","record":{"aliases":["GHSA-92wr-j974-xw8j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"RSA BSAFE Crypto-J","requires_auth":"none","summary":"A remote attacker can recover RSA keys via a timing channel attack in RSA BSAFE libraries, compromising encrypted data confidentiality.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"bsafe_crypto-j","vendor":"dell"},{"product":"rsa_bsafe_ssl-j","vendor":"dell"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"RSA BSAFE Crypto-J versions prior to 6.2.4 and RSA BSAFE SSL-J versions prior to 6.2.4 contain a Covert Timing Channel vulnerability during PKCS #1 unpadding operations, also known as a Bleichenbacher attack. A remote attacker may be able to recover a RSA key.","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":"Weak cryptography in RSA BSAFE Crypto-J","id":"CVE-2018-11070","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"DSA-2018-147: Dell EMC Isilon OneFS and IsilonSD Edge Remote Process Crash Vulnerability","id":"CVE-2018-11071"},"packages":[],"prev":{"headline":"Weak cryptography in RSA BSAFE SSL-J","id":"CVE-2018-11069"},"products":["RSA BSAFE Crypto-J","RSA BSAFE SSL-J"],"published":"2018-09-11","related":[{"cvss_score":9.1,"headline":"Supply chain in Dell BSAFE Crypto-J","id":"CVE-2022-34381","kev_date_added":null,"published":"2024-02-02"},{"cvss_score":7.5,"headline":"Security feature bypass in RSA BSAFE Crypto-J RSA BSAFE Crypto-J versions prior to 6.2.2","id":"CVE-2016-8212","kev_date_added":null,"published":"2017-02-03"},{"cvss_score":5.9,"headline":"Information disclosure in BSAFE Crypto-J","id":"CVE-2025-26333","kev_date_added":null,"published":"2025-09-25"},{"cvss_score":3.7,"headline":"Information disclosure in RSA BSAFE Crypto-J RSA BSAFE Crypto-J versions prior to 6.2.2","id":"CVE-2016-8217","kev_date_added":null,"published":"2017-02-03"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Dell EMC"]},"summary":"A remote attacker can recover RSA keys via a timing channel attack in RSA BSAFE libraries, compromising encrypted data confidentiality.","url":"https://insights.sbomify.com/CVE-2018-11070/"}