{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-9387 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-9387 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-9387 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Jun 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-9387 and fix it if it is affected.\n\nWhat it is: CVE-2017-9387 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Jun 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-9387 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-2017-9387/ (Markdown: https://insights.sbomify.com/CVE-2017-9387/index.md)","id":"CVE-2017-9387","markdown":"https://insights.sbomify.com/CVE-2017-9387/index.md","name":"CVE-2017-9387","record":{"aliases":["GHSA-qmjg-23p5-mqr3"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Vera home automation","requires_auth":"low_privilege","summary":"Stored XSS in Vera devices allows attackers to execute malicious scripts in user browsers via log file injection.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"veraedge_firmware","vendor":"getvera"},{"product":"veralite_firmware","vendor":"getvera"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/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":"An issue was discovered on Vera VeraEdge 1.7.19 and Veralite 1.7.481 devices. The device provides a shell script called relay.sh which is used for creating new SSH relays for the device so that the device connects to Vera servers. All the parameters passed in this specific script are logged to a log file called log.relay in the /tmp folder. The user can also read all the log files from the device using a script called log.sh. However, when the script loads the log files it displays them with content-type text/html and passes all the logs through the ansi2html binary which converts all the character text including HTML meta-characters correctly to be displayed in the browser. This allows an attacker to use the log files as a storing mechanism for the XSS payload and thus whenever a user navigates to that log.sh script, it enables the XSS payload and allows an attacker to execute his malicious payload on the user's browser.","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-2017-9387","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2017-9388"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2017-9386"},"products":["n/a"],"published":"2019-06-17","related":[{"cvss_score":9.9,"headline":"Server-side request forgery in n/a","id":"CVE-2017-9383","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2017-9385","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-9381","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-9384","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-9388","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2017-9389","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-9391","kev_date_added":null,"published":"2019-06-17"}],"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":"Stored XSS in Vera devices allows attackers to execute malicious scripts in user browsers via log file injection.","url":"https://insights.sbomify.com/CVE-2017-9387/"}