{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1575 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-1575 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-1575 is a medium-severity vulnerability in Ibm Sterling File Gateway, published on 20 Jul 2018. 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-2017-1575 and fix it if it is affected.\n\nWhat it is: CVE-2017-1575 is a medium-severity vulnerability in Ibm Sterling File Gateway, published on 20 Jul 2018. 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-2017-1575 in the wild and no public exploit code.\n\nAffected product: Ibm Sterling File Gateway. 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-2017-1575/ (Markdown: https://insights.sbomify.com/CVE-2017-1575/index.md)","id":"CVE-2017-1575","markdown":"https://insights.sbomify.com/CVE-2017-1575/index.md","name":"CVE-2017-1575","record":{"aliases":["GHSA-92cp-f5fr-233x"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM Sterling File Gateway","requires_auth":"none","summary":"A local attacker can decrypt highly sensitive information due to the use of weak cryptographic algorithms in IBM Sterling File Gateway.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"sterling_file_gateway","vendor":"ibm"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:3.0/A:N/AC:H/AV:L/C:H/I:N/PR:N/S:U/UI:N/E:U/RC:C/RL:O","version":"3.0"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"IBM Sterling B2B Integrator Standard Edition (IBM Sterling File Gateway 2.2.0 through 2.2.6) uses weaker than expected cryptographic algorithms that could allow a local attacker to decrypt highly sensitive information. IBM X-Force ID: 132032.","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 Sterling File Gateway","id":"CVE-2017-1575","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:sterling_file_gateway","products":["ibm:sterling_file_gateway"],"type":"weak_cryptography","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in WebSphere Portal","id":"CVE-2017-1577"},"packages":[],"prev":{"headline":"Weak cryptography in DB2 for Linux, UNIX and Windows","id":"CVE-2017-1571"},"products":["Sterling File Gateway"],"published":"2018-07-20","related":[{"cvss_score":6.5,"headline":"Missing authorization in Sterling File Gateway","id":"CVE-2020-4259","kev_date_added":null,"published":"2020-05-14"},{"cvss_score":6.5,"headline":"Missing authorization in Sterling File Gateway","id":"CVE-2017-1550","kev_date_added":null,"published":"2017-12-11"},{"cvss_score":6.5,"headline":"Information disclosure in Sterling File Gateway","id":"CVE-2017-1487","kev_date_added":null,"published":"2017-12-07"},{"cvss_score":6.4,"headline":"IBM Sterling File Gateway cross-site scripting","id":"CVE-2023-52292","kev_date_added":null,"published":"2025-01-27"},{"cvss_score":6.3,"headline":"Auth bypass in Sterling File Gateway","id":"CVE-2021-20473","kev_date_added":null,"published":"2021-10-07"},{"cvss_score":6.3,"headline":"SQL injection in Sterling File Gateway","id":"CVE-2020-4647","kev_date_added":null,"published":"2020-11-16"},{"cvss_score":6.1,"headline":"Cross-site scripting in Sterling File Gateway","id":"CVE-2020-4658","kev_date_added":null,"published":"2020-12-16"}],"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":["IBM"]},"summary":"A local attacker can decrypt highly sensitive information due to the use of weak cryptographic algorithms in IBM Sterling File Gateway.","url":"https://insights.sbomify.com/CVE-2017-1575/"}