{"answers":{"affected":"2 open source packages ship an affected version, including devise_token_auth. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16751 in the wild and no public exploit code.","fix":"Upgrade devise_token_auth to 1.1.3 or later.","what":"CVE-2019-16751 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Sep 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-16751 and fix it if it is affected.\n\nWhat it is: CVE-2019-16751 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Sep 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-16751 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- devise_token_auth (RubyGems): affected from 0.1.33; fixed in 1.1.3\n- devise_token_auth (RubyGems): affected from 0.1.33; fixed in 1.1.3\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-16751/ (Markdown: https://insights.sbomify.com/CVE-2019-16751/index.md)","id":"CVE-2019-16751","markdown":"https://insights.sbomify.com/CVE-2019-16751/index.md","name":"CVE-2019-16751","record":{"aliases":["GHSA-mvqr-r76c-wm5f"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby authentication library","requires_auth":"none","summary":"Unauthenticated attackers can execute malicious JavaScript in victims' browsers via a crafted URL in the Devise Token Auth library.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"devise_token_auth","vendor":"devise_token_auth_project"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"An issue was discovered in Devise Token Auth through 1.1.2. The omniauth failure endpoint is vulnerable to Reflected Cross Site Scripting (XSS) through the message parameter. Unauthenticated attackers can craft a URL that executes a malicious JavaScript payload in the victim's browser. This affects the fallback_render method in the omniauth callbacks controller.","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":"Devise Token Auth vulnerable to Cross-site Scripting","id":"CVE-2019-16751","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"xss","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2019-16752"},"packages":[{"ecosystem":"RubyGems","fixed":["1.1.3"],"introduced":["0.1.33"],"last_affected":[],"package":"devise_token_auth","purl":null,"source":"GHSA-mvqr-r76c-wm5f"},{"ecosystem":"RubyGems","fixed":["1.1.3"],"introduced":["0.1.33"],"last_affected":[],"package":"devise_token_auth","purl":"pkg:gem/devise_token_auth","source":"GHSA-mvqr-r76c-wm5f"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-16748"},"products":["n/a"],"published":"2019-09-24","related":[],"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-05","vendors":["n/a"]},"summary":"Unauthenticated attackers can execute malicious JavaScript in victims' browsers via a crafted URL in the Devise Token Auth library.","url":"https://insights.sbomify.com/CVE-2019-16751/"}