{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-41897 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-41897 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-41897 is a high-severity cross-site scripting vulnerability in home-assistant core, published on 19 Oct 2023. 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-2023-41897 and fix it if it is affected.\n\nWhat it is: CVE-2023-41897 is a high-severity cross-site scripting vulnerability in home-assistant core, published on 19 Oct 2023. 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-2023-41897 in the wild and no public exploit code.\n\nAffected product: home-assistant core. 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-2023-41897/ (Markdown: https://insights.sbomify.com/CVE-2023-41897/index.md)","id":"CVE-2023-41897","markdown":"https://insights.sbomify.com/CVE-2023-41897/index.md","name":"CVE-2023-41897","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Home automation server","requires_auth":"none","summary":"Missing X-Frame-Options header allows clickjacking, enabling attackers to trick users into installing malicious add-ons for remote code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"home-assistant","vendor":"home-assistant"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1021","name":"Improper Restriction of Rendered UI Layers or Frames"}],"description":"Home assistant is an open source home automation. Home Assistant server does not set any HTTP security headers, including the X-Frame-Options header, which specifies whether the web page is allowed to be framed. The omission of this and correlating headers facilitates covert clickjacking attacks and alternative exploit opportunities, such as the vector described in this security advisory. This fault incurs major risk, considering the ability to trick users into installing an external and malicious add-on with minimal user interaction, which would enable Remote Code Execution (RCE) within the Home Assistant application. This issue has been addressed in version 2023.9.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.","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":"Lack of XFO header allows clickjacking in Home Assistant Core","id":"CVE-2023-41897","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Arbitrary URL load in Android WebView in `MyActivity.kt` in Home Assistant Companion for Android","id":"CVE-2023-41898"},"packages":[],"prev":{"headline":"Fake websocket server installation permits full takeover in Home Assistant Core","id":"CVE-2023-41896"},"products":["core"],"published":"2023-10-19","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":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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-12","vendors":["home-assistant"]},"summary":"Missing X-Frame-Options header allows clickjacking, enabling attackers to trick users into installing malicious add-ons for remote code execution.","url":"https://insights.sbomify.com/CVE-2023-41897/"}