{"answers":{"affected":"2 open source packages ship an affected version, including activerecord. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6317 in the wild and no public exploit code.","fix":"Upgrade activerecord to 4.2.7.1 or later.","what":"CVE-2016-6317 is a high-severity SQL injection vulnerability in Rubyonrails Rails, published on 7 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-6317 and fix it if it is affected.\n\nWhat it is: CVE-2016-6317 is a high-severity SQL injection vulnerability in Rubyonrails Rails, published on 7 Sep 2016. 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-2016-6317 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- activerecord (RubyGems): affected from 4.2.0; fixed in 4.2.7.1\n- activerecord (RubyGems): affected from 4.2.0; fixed in 4.2.7.1\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-2016-6317/ (Markdown: https://insights.sbomify.com/CVE-2016-6317/index.md)","id":"CVE-2016-6317","markdown":"https://insights.sbomify.com/CVE-2016-6317/index.md","name":"CVE-2016-6317","record":{"aliases":["DEBIAN-CVE-2016-6317","GHSA-pr3r-4wrp-r2pv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby on Rails","requires_auth":"none","summary":"Remote attackers can bypass database query restrictions and trigger missing WHERE clauses via crafted requests, potentially exposing or modifying data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"rails","vendor":"rubyonrails"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"Action Record in Ruby on Rails 4.2.x before 4.2.7.1 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request, as demonstrated by certain \"[nil]\" values, a related issue to CVE-2012-2660, CVE-2012-2694, and CVE-2013-0155.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":"2017-09-26","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2017-09-26T16:42:26Z","kind":"github_poc","ref":"https://github.com/kavgan/vuln_test_repo_public_ruby_gemfile_cve-2016-6317","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"ActiveRecord in Ruby on Rails allows database-query bypass","id":"CVE-2016-6317","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":"rubyonrails:rails","products":["rubyonrails:rails"],"type":"sql_injection","year":"2016"},"n_packages":2,"n_references":5,"next":{"headline":"Memory corruption in n/a","id":"CVE-2016-6318"},"packages":[{"ecosystem":"RubyGems","fixed":["4.2.7.1"],"introduced":["4.2.0"],"last_affected":[],"package":"activerecord","purl":null,"source":"GHSA-pr3r-4wrp-r2pv"},{"ecosystem":"RubyGems","fixed":["4.2.7.1"],"introduced":["4.2.0"],"last_affected":[],"package":"activerecord","purl":"pkg:gem/activerecord","source":"GHSA-pr3r-4wrp-r2pv"}],"prev":{"headline":"actionview Cross-site Scripting vulnerability","id":"CVE-2016-6316"},"products":["n/a"],"published":"2016-09-07","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.1,"headline":"SQL injection in n/a","id":"CVE-2017-17917","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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can bypass database query restrictions and trigger missing WHERE clauses via crafted requests, potentially exposing or modifying data.","url":"https://insights.sbomify.com/CVE-2016-6317/"}