{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1670 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-1670 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-1670 is a critical SQL injection vulnerability in Ibm Security Key Lifecycle Manager, published on 9 Jan 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-2017-1670 and fix it if it is affected.\n\nWhat it is: CVE-2017-1670 is a critical SQL injection vulnerability in Ibm Security Key Lifecycle Manager, published on 9 Jan 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-2017-1670 in the wild and no public exploit code.\n\nAffected product: Ibm Security Key Lifecycle Manager. 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-1670/ (Markdown: https://insights.sbomify.com/CVE-2017-1670/index.md)","id":"CVE-2017-1670","markdown":"https://insights.sbomify.com/CVE-2017-1670/index.md","name":"CVE-2017-1670","record":{"aliases":["GHSA-8gpr-xf5x-5gg8"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Key Lifecycle Manager","requires_auth":"none","summary":"Remote attackers can execute SQL commands to view, add, modify, or delete database information in IBM Tivoli Key Lifecycle Manager.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_key_lifecycle_manager","vendor":"ibm"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 133637.","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":"SQL injection in Security Key Lifecycle Manager","id":"CVE-2017-1670","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:security_key_lifecycle_manager","products":["ibm:security_key_lifecycle_manager"],"type":"sql_injection","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in Security Key Lifecycle Manager","id":"CVE-2017-1671"},"packages":[],"prev":{"headline":"Information disclosure in Security Key Lifecycle Manager","id":"CVE-2017-1669"},"products":["Security Key Lifecycle Manager"],"published":"2018-01-09","related":[{"cvss_score":9.8,"headline":"Weak cryptography in Security Key Lifecycle Manager","id":"CVE-2016-6093","kev_date_added":null,"published":"2017-06-08"},{"cvss_score":9.8,"headline":"Security feature bypass in Key Lifecycle Manager","id":"CVE-2016-6095","kev_date_added":null,"published":"2017-02-02"},{"cvss_score":8.8,"headline":"Cross-site request forgery in Security Key Lifecycle Manager","id":"CVE-2017-1672","kev_date_added":null,"published":"2018-01-04"},{"cvss_score":8.8,"headline":"Cross-site request forgery in Key Lifecycle Manager","id":"CVE-2016-6103","kev_date_added":null,"published":"2017-02-02"},{"cvss_score":8.6,"headline":"Security feature bypass in Security Key Lifecycle Manager","id":"CVE-2020-4567","kev_date_added":null,"published":"2020-07-29"},{"cvss_score":8.2,"headline":"Missing authorization in Key Lifecycle Manager","id":"CVE-2016-6105","kev_date_added":null,"published":"2017-02-01"}],"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-17","vendors":["IBM"]},"summary":"Remote attackers can execute SQL commands to view, add, modify, or delete database information in IBM Tivoli Key Lifecycle Manager.","url":"https://insights.sbomify.com/CVE-2017-1670/"}