{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-17309 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-17309 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-17309 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Sep 2018. 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-2018-17309 and fix it if it is affected.\n\nWhat it is: CVE-2018-17309 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Sep 2018. 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-2018-17309 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2018-17309/ (Markdown: https://insights.sbomify.com/CVE-2018-17309/index.md)","id":"CVE-2018-17309","markdown":"https://insights.sbomify.com/CVE-2018-17309/index.md","name":"CVE-2018-17309","record":{"aliases":["GHSA-vwf3-jw47-rmv3"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"RICOH printer","requires_auth":"none","summary":"Attackers can inject malicious scripts via the entryNameIn parameter in the address wizard, potentially leading to session hijacking or code execution on the printer interface.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mp_c406zspf_firmware","vendor":"ricoh"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"On the RICOH MP C406Z printer, HTML Injection and Stored XSS vulnerabilities have been discovered in the area of adding addresses via the entryNameIn parameter to /web/entry/en/address/adrsSetUserWizard.cgi.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2018-17309","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-17310"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2018-17305"},"products":["n/a"],"published":"2018-09-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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 malicious scripts via the entryNameIn parameter in the address wizard, potentially leading to session hijacking or code execution on the printer interface.","url":"https://insights.sbomify.com/CVE-2018-17309/"}