{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-17917 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-17917 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-17917 is a high-severity SQL injection vulnerability in Rubyonrails Rails, published on 29 Dec 2017. 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-17917 and fix it if it is affected.\n\nWhat it is: CVE-2017-17917 is a high-severity SQL injection vulnerability in Rubyonrails Rails, published on 29 Dec 2017. 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-17917 in the wild and no public exploit code.\n\nAffected product: Rubyonrails Rails. 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-17917/ (Markdown: https://insights.sbomify.com/CVE-2017-17917/index.md)","id":"CVE-2017-17917","markdown":"https://insights.sbomify.com/CVE-2017-17917/index.md","name":"CVE-2017-17917","record":{"aliases":["DEBIAN-CVE-2017-17917","GHSA-vqpc-h5g8-fhrw"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby on Rails","requires_auth":"none","summary":"Remote attackers can execute arbitrary SQL commands via the id parameter in the where method, potentially compromising data integrity and confidentiality.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rails","vendor":"rubyonrails"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SQL injection vulnerability in the 'where' method in Ruby on Rails 5.1.4 and earlier allows remote attackers to execute arbitrary SQL commands via the 'id' parameter. NOTE: The vendor disputes this issue because the documentation states that this method is not intended for use with untrusted input","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-01-18","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-01-18T22:12:54Z","kind":"github_poc","ref":"https://github.com/matiasarenhard/rails-cve-2017-17917","stars":1,"title":null}],"tier":"poc_unverified"},"has_fix":false,"headline":"SQL injection in n/a","id":"CVE-2017-17917","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"rubyonrails:rails","products":["rubyonrails:rails"],"type":"sql_injection","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2017-17919"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2017-17916"},"products":["n/a"],"published":"2017-12-29","related":[{"cvss_score":10,"headline":"Active Record contains deserialization of arbitrary YAML","id":"CVE-2013-0277","kev_date_added":null,"published":"2013-02-13"},{"cvss_score":8.1,"headline":"SQL injection in n/a","id":"CVE-2017-17916","kev_date_added":null,"published":"2017-12-29"},{"cvss_score":8,"headline":"Rails Active Storage has possible Path Traversal in DiskService","id":"CVE-2026-33195","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":7.5,"headline":"Rails possible ReDoS vulnerability in Accept header parsing in Action Dispatch","id":"CVE-2024-26142","kev_date_added":null,"published":"2024-02-27"},{"cvss_score":7.5,"headline":"ReDoS based DoS vulnerability in Action Dispatch","id":"CVE-2023-22792","kev_date_added":null,"published":"2023-02-09"},{"cvss_score":7.5,"headline":"Denial of Service in Action Dispatch","id":"CVE-2021-22902","kev_date_added":null,"published":"2021-06-11"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary SQL commands via the id parameter in the where method, potentially compromising data integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2017-17917/"}