{"answers":{"affected":"2 open source packages ship an affected version, including activerecord. It affects 2 products.","exploited":"There is no known exploitation of CVE-2013-3221 in the wild and no public exploit code.","fix":"Upgrade activerecord to 4.2.0 or later.","what":"CVE-2013-3221 is a medium-severity SQL injection vulnerability in Rubyonrails Rails, published on 22 Apr 2013. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-3221 and fix it if it is affected.\n\nWhat it is: CVE-2013-3221 is a medium-severity SQL injection vulnerability in Rubyonrails Rails, published on 22 Apr 2013. It can be exploited over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2013-3221 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- activerecord (RubyGems): affected all versions; fixed in 4.2.0\n- activerecord (RubyGems): affected all versions; fixed in 4.2.0\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-2013-3221/ (Markdown: https://insights.sbomify.com/CVE-2013-3221/index.md)","id":"CVE-2013-3221","markdown":"https://insights.sbomify.com/CVE-2013-3221/index.md","name":"CVE-2013-3221","record":{"aliases":["DEBIAN-CVE-2013-3221","GHSA-f57c-hx33-hvh8"],"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":"unknown","summary":"Remote attackers can manipulate database queries via crafted input in Ruby on Rails applications, potentially reading or modifying data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rails","vendor":"rubyonrails"},{"product":"ruby_on_rails","vendor":"rubyonrails"}],"cvss":{"score":6.4,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The Active Record component in Ruby on Rails 2.3.x, 3.0.x, 3.1.x, and 3.2.x does not ensure that the declared data type of a database column is used during comparisons of input values to stored values in that column, which makes it easier for remote attackers to conduct data-type injection attacks against Ruby on Rails applications via a crafted value, as demonstrated by unintended interaction between the \"typed XML\" feature and a MySQL database.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Active Record component in Ruby on Rails has a data-type injection vulnerability","id":"CVE-2013-3221","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":"rubyonrails:rails","products":["rubyonrails:rails"],"type":"sql_injection","year":"2013"},"n_packages":2,"n_references":6,"next":{"headline":"Information disclosure in n/a","id":"CVE-2013-3222"},"packages":[{"ecosystem":"RubyGems","fixed":["4.2.0"],"introduced":["0"],"last_affected":[],"package":"activerecord","purl":null,"source":"GHSA-f57c-hx33-hvh8"},{"ecosystem":"RubyGems","fixed":["4.2.0"],"introduced":["0"],"last_affected":[],"package":"activerecord","purl":"pkg:gem/activerecord","source":"GHSA-f57c-hx33-hvh8"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2013-3220"},"products":["n/a"],"published":"2013-04-22","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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can manipulate database queries via crafted input in Ruby on Rails applications, potentially reading or modifying data.","url":"https://insights.sbomify.com/CVE-2013-3221/"}