{"answers":{"affected":"2 open source packages ship an affected version, including field_test. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-13146 in the wild and no public exploit code.","fix":"Upgrade field_test to 0.3.1 or later.","what":"CVE-2019-13146 is a medium-severity vulnerability in n/a, published on 9 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-13146 and fix it if it is affected.\n\nWhat it is: CVE-2019-13146 is a medium-severity vulnerability in n/a, published on 9 Jul 2019. 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-2019-13146 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- field_test (RubyGems): affected from 0.3.0; fixed in 0.3.1\n- field_test (RubyGems): affected from 0.3.0; fixed in 0.3.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-2019-13146/ (Markdown: https://insights.sbomify.com/CVE-2019-13146/index.md)","id":"CVE-2019-13146","markdown":"https://insights.sbomify.com/CVE-2019-13146/index.md","name":"CVE-2019-13146","record":{"aliases":["GHSA-wg9m-gw3h-hg83"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby field_test gem","requires_auth":"none","summary":"The field_test gem allows unvalidated input to return arbitrary values, potentially enabling downstream vulnerabilities like SQL injection or XSS in dependent applications.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"field_test","vendor":"field_test_project"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"The field_test gem 0.3.0 for Ruby has unvalidated input. A method call that is expected to return a value from a certain set of inputs can be made to return any input, which can be dangerous depending on how applications use it. If an application treats arbitrary variants as trusted, this can lead to a variety of potential vulnerabilities like SQL injection or cross-site scripting (XSS).","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":"field_test gem contains injection vulnerability","id":"CVE-2019-13146","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"other","year":"2019"},"n_packages":2,"n_references":3,"next":{"headline":"Null dereference in n/a","id":"CVE-2019-13147"},"packages":[{"ecosystem":"RubyGems","fixed":["0.3.1"],"introduced":["0.3.0"],"last_affected":[],"package":"field_test","purl":null,"source":"GHSA-wg9m-gw3h-hg83"},{"ecosystem":"RubyGems","fixed":["0.3.1"],"introduced":["0.3.0"],"last_affected":[],"package":"field_test","purl":"pkg:gem/field_test","source":"GHSA-wg9m-gw3h-hg83"}],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-13145"},"products":["n/a"],"published":"2019-07-09","related":[{"cvss_score":4.3,"headline":"Field Test CSRF vulnerability","id":"CVE-2020-16252","kev_date_added":null,"published":"2020-08-05"}],"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-04","vendors":["n/a"]},"summary":"The field_test gem allows unvalidated input to return arbitrary values, potentially enabling downstream vulnerabilities like SQL injection or XSS in dependent applications.","url":"https://insights.sbomify.com/CVE-2019-13146/"}