# CVE-2023-41895: Cross-site Scripting via auth_callback login in Home Assistant Core > Attackers can execute arbitrary JavaScript on the Home Assistant login page via crafted redirect URIs, potentially leading to full account takeover. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 19 Oct 2023 - **Updated:** 12 Sep 2024 - **Also known as:** GHSA-jvxq-x42r-f7mv ## What is CVE-2023-41895? CVE-2023-41895 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. ### Official description Home assistant is an open source home automation. The Home Assistant login page allows users to use their local Home Assistant credentials and log in to another website that specifies the `redirect_uri` and `client_id` parameters. Although the `redirect_uri` validation typically ensures that it matches the `client_id` and the scheme represents either `http` or `https`, Home Assistant will fetch the `client_id` and check for `` HTML tags on the page. These URLs are not subjected to the same scheme validation and thus allow for arbitrary JavaScript execution on the Home Assistant administration page via usage of `javascript:` scheme URIs. This Cross-site Scripting (XSS) vulnerability can be executed on the Home Assistant frontend domain, which may be used for a full takeover of the Home Assistant account and installation. 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. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2023-41895? It affects 1 product. Products: Home-Assistant Home-Assistant. ## How do I fix CVE-2023-41895? No fix has been published for CVE-2023-41895 yet. Limit exposure of the affected software until one is available. ## Is CVE-2023-41895 being exploited? There is no known exploitation of CVE-2023-41895 in the wild and no public exploit code. ## Other vulnerabilities in home-assistant core - [CVE-2023-27482](https://insights.sbomify.com/CVE-2023-27482/): Auth bypass in core (critical 10.0) - [CVE-2023-41897](https://insights.sbomify.com/CVE-2023-41897/): Lack of XFO header allows clickjacking in Home Assistant Core (high 8.8) - [CVE-2026-54317](https://insights.sbomify.com/CVE-2026-54317/): Home Assistant: Konnected alarm-panel switch state and zone topology disclosed to unauthenticated actors on the LAN (high 7.6) - [CVE-2020-36517](https://insights.sbomify.com/CVE-2020-36517/): Information disclosure in n/a (high 7.5) - [CVE-2018-21019](https://insights.sbomify.com/CVE-2018-21019/): Home Assistant information disclosure vulnerability (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-41895 and fix it if it is affected. What it is: CVE-2023-41895 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. Exploitation: There is no known exploitation of CVE-2023-41895 in the wild and no public exploit code. Affected product: home-assistant core. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-41895/ (Markdown: https://insights.sbomify.com/CVE-2023-41895/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-41895 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-41895 - OSV: https://osv.dev/vulnerability/CVE-2023-41895 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-41895/ Summaries are generated and may contain mistakes; the official description above is the record.