{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16782 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16782 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16782 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 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-16782 and fix it if it is affected.\n\nWhat it is: CVE-2017-16782 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 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-16782 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-16782/ (Markdown: https://insights.sbomify.com/CVE-2017-16782/index.md)","id":"CVE-2017-16782","markdown":"https://insights.sbomify.com/CVE-2017-16782/index.md","name":"CVE-2017-16782","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Home Assistant","requires_auth":"none","summary":"Attackers can inject JavaScript into persistent notifications via crafted Markdown, potentially leading to code execution or account takeover in Home Assistant.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"home-assistant","vendor":"home-assistant"}],"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":"In Home Assistant before 0.57, it is possible to inject JavaScript code into a persistent notification via crafted Markdown text, aka XSS.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2017-16782","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in n/a","id":"CVE-2017-16783"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-16781"},"products":["n/a"],"published":"2017-11-10","related":[{"cvss_score":10,"headline":"Auth bypass in core","id":"CVE-2023-27482","kev_date_added":null,"published":"2023-03-08"},{"cvss_score":8.8,"headline":"Cross-site Scripting via auth_callback login in Home Assistant Core","id":"CVE-2023-41895","kev_date_added":null,"published":"2023-10-19"},{"cvss_score":8.8,"headline":"Lack of XFO header allows clickjacking in Home Assistant Core","id":"CVE-2023-41897","kev_date_added":null,"published":"2023-10-19"},{"cvss_score":7.6,"headline":"Home Assistant: Konnected alarm-panel switch state and zone topology disclosed to unauthenticated actors on the LAN","id":"CVE-2026-54317","kev_date_added":null,"published":"2026-06-23"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-36517","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":7.5,"headline":"Home Assistant information disclosure vulnerability","id":"CVE-2018-21019","kev_date_added":null,"published":"2019-09-23"},{"cvss_score":7.3,"headline":"Home Assistant has stored XSS in Map-card through malicious device name","id":"CVE-2026-33044","kev_date_added":null,"published":"2026-03-27"}],"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 JavaScript into persistent notifications via crafted Markdown, potentially leading to code execution or account takeover in Home Assistant.","url":"https://insights.sbomify.com/CVE-2017-16782/"}