{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-23347 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-23347 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-23347 is a medium-severity vulnerability in HCL DRYiCE iAutomate, published on 9 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-23347 and fix it if it is affected.\n\nWhat it is: CVE-2023-23347 is a medium-severity vulnerability in HCL DRYiCE iAutomate, published on 9 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-23347 in the wild and no public exploit code.\n\nAffected product: HCL DRYiCE iAutomate. 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-2023-23347/ (Markdown: https://insights.sbomify.com/CVE-2023-23347/index.md)","id":"CVE-2023-23347","markdown":"https://insights.sbomify.com/CVE-2023-23347/index.md","name":"CVE-2023-23347","record":{"aliases":["GHSA-ph2h-6cc9-xf5r"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"HCL DRYiCE iAutomate","requires_auth":"low_privilege","summary":"An attacker can compromise the confidentiality and integrity of sensitive information in HCL DRYiCE iAutomate due to the use of a broken cryptographic algorithm.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HCL","cpe":[{"product":"dryice_iautomate","vendor":"hcltech"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"HCL DRYiCE iAutomate is affected by the use of a broken cryptographic algorithm.  An attacker can potentially compromise the confidentiality and integrity of sensitive information.","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":"Use of a broken cryptographic algorithm affects HCL DRYiCE iAutomate","id":"CVE-2023-23347","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"HCL Launch is vulnerable to sensitive information disclosure","id":"CVE-2023-23348"},"packages":[],"prev":{"headline":"Use of a broken cryptographic algorithm affects HCL DRYiCE MyCloud","id":"CVE-2023-23346"},"products":["HCL DRYiCE iAutomate"],"published":"2023-08-09","related":[{"cvss_score":7.6,"headline":"HCL iAutomate is affected by a sensitive data exposure vulnerability","id":"CVE-2025-31955","kev_date_added":null,"published":"2025-07-24"},{"cvss_score":7.1,"headline":"HCL iAutomate is affected by an insufficient session expiration","id":"CVE-2025-31952","kev_date_added":null,"published":"2025-07-24"},{"cvss_score":7.1,"headline":"HCL iAutomate is affected by hardcoded credentials","id":"CVE-2025-31953","kev_date_added":null,"published":"2025-07-24"},{"cvss_score":5.5,"headline":"HCL iAutomate is affected by a session fixation vulnerability","id":"CVE-2024-42207","kev_date_added":null,"published":"2025-02-05"},{"cvss_score":5.4,"headline":"HCL iAutomate is susceptible to a sensitive information disclosure","id":"CVE-2025-31954","kev_date_added":null,"published":"2025-11-05"}],"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":"2024-10-29","vendors":["HCL Software"]},"summary":"An attacker can compromise the confidentiality and integrity of sensitive information in HCL DRYiCE iAutomate due to the use of a broken cryptographic algorithm.","url":"https://insights.sbomify.com/CVE-2023-23347/"}