{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-1701 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-1701 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-1701 is a high-severity vulnerability in Ibm Rational Collaborative Lifecycle Management, published on 23 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1701 and fix it if it is affected.\n\nWhat it is: CVE-2017-1701 is a high-severity vulnerability in Ibm Rational Collaborative Lifecycle Management, published on 23 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-1701 in the wild and no public exploit code.\n\nAffected product: Ibm Rational Collaborative Lifecycle Management. 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-1701/ (Markdown: https://insights.sbomify.com/CVE-2017-1701/index.md)","id":"CVE-2017-1701","markdown":"https://insights.sbomify.com/CVE-2017-1701/index.md","name":"CVE-2017-1701","record":{"aliases":["GHSA-rg22-25wr-x484"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Rational Team Concert","requires_auth":"low_privilege","summary":"An authenticated user can obtain highly sensitive information due to weak encryption of stored credentials in IBM Team Concert.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"rational_collaborative_lifecycle_management","vendor":"ibm"},{"product":"rational_team_concert","vendor":"ibm"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"IBM Team Concert (RTC) 5.0, 5.0.1, 5.0.2, 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, and 6.0.5 stores credentials for users using a weak encryption algorithm, which could allow an authenticated user to obtain highly sensitive information. IBM X-Force ID: 134393.","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 Rational Team Concert","id":"CVE-2017-1701","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:rational_collaborative_lifecycle_management","products":["ibm:rational_collaborative_lifecycle_management","ibm:rational_team_concert"],"type":"weak_cryptography","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Security Privileged Identity Manager","id":"CVE-2017-1705"},"packages":[],"prev":{"headline":"Missing authorization in Rational Collaborative Lifecycle Management","id":"CVE-2017-1700"},"products":["Rational Team Concert"],"published":"2018-04-23","related":[{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2014-0862","kev_date_added":null,"published":"2014-03-02"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2016-0326","kev_date_added":null,"published":"2016-10-22"},{"cvss_score":8.1,"headline":"XML external entity in Rational Collaborative Lifecycle Management","id":"CVE-2016-9707","kev_date_added":null,"published":"2017-03-31"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2015-7440","kev_date_added":null,"published":"2018-03-15"},{"cvss_score":6.8,"headline":"Information disclosure in Rational Collaborative Lifecycle Management","id":"CVE-2016-2981","kev_date_added":null,"published":"2017-03-20"},{"cvss_score":6.8,"headline":"Other in n/a","id":"CVE-2015-1928","kev_date_added":null,"published":"2016-01-02"}],"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":"An authenticated user can obtain highly sensitive information due to weak encryption of stored credentials in IBM Team Concert.","url":"https://insights.sbomify.com/CVE-2017-1701/"}