{"answers":{"affected":"2 open source packages ship an affected version, including geminabox. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16792 in the wild and no public exploit code.","fix":"Upgrade geminabox to 0.13.10 or later.","what":"CVE-2017-16792 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Nov 2017. 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-2017-16792 and fix it if it is affected.\n\nWhat it is: CVE-2017-16792 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Nov 2017. 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-2017-16792 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- geminabox (RubyGems): affected all versions; fixed in 0.13.10\n- geminabox (RubyGems): affected all versions; fixed in 0.13.10\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-16792/ (Markdown: https://insights.sbomify.com/CVE-2017-16792/index.md)","id":"CVE-2017-16792","markdown":"https://insights.sbomify.com/CVE-2017-16792/index.md","name":"CVE-2017-16792","record":{"aliases":["GHSA-653m-r33x-39ff"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby gem hosting","requires_auth":"none","summary":"Attackers can inject arbitrary web script via the homepage field in gemspec files, potentially compromising users of the Gem in a Box application.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"geminabox","vendor":"geminabox_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":"Stored cross-site scripting (XSS) vulnerability in \"geminabox\" (Gem in a Box) before 0.13.10 allows attackers to inject arbitrary web script via the \"homepage\" value of a \".gemspec\" file, related to views/gem.erb and views/index.erb.","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":"Geminabox contains Cross-site Scripting","id":"CVE-2017-16792","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"xss","year":"2017"},"n_packages":2,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2017-16793"},"packages":[{"ecosystem":"RubyGems","fixed":["0.13.10"],"introduced":["0"],"last_affected":[],"package":"geminabox","purl":null,"source":"GHSA-653m-r33x-39ff"},{"ecosystem":"RubyGems","fixed":["0.13.10"],"introduced":["0"],"last_affected":[],"package":"geminabox","purl":"pkg:gem/geminabox","source":"GHSA-653m-r33x-39ff"}],"prev":{"headline":"Symfony SSRF Vulnerability via Form Component","id":"CVE-2017-16790"},"products":["n/a"],"published":"2017-11-13","related":[{"cvss_score":8.8,"headline":"Gem in a Box vulnerable to Cross-site Request Forgery","id":"CVE-2017-14683","kev_date_added":null,"published":"2017-09-25"},{"cvss_score":5.4,"headline":"Gem in a Box vulnerable to Cross-site Scripting","id":"CVE-2017-14506","kev_date_added":null,"published":"2017-09-25"}],"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":"Attackers can inject arbitrary web script via the homepage field in gemspec files, potentially compromising users of the Gem in a Box application.","url":"https://insights.sbomify.com/CVE-2017-16792/"}