# CVE-2023-41897: Lack of XFO header allows clickjacking in Home Assistant Core

> Missing X-Frame-Options header allows clickjacking, enabling attackers to trick users into installing malicious add-ons for remote code execution.

- **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

## What is CVE-2023-41897?

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.

### Official 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.

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames)

## Which versions are affected by CVE-2023-41897?

It affects 1 product.


Products: Home-Assistant Home-Assistant.

## How do I fix CVE-2023-41897?

No fix has been published for CVE-2023-41897 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-41897 being exploited?

There is no known exploitation of CVE-2023-41897 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-41895](https://insights.sbomify.com/CVE-2023-41895/): Cross-site Scripting via auth_callback login 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-41897 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2023-41897 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-41897/ (Markdown: https://insights.sbomify.com/CVE-2023-41897/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-41897
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-41897
- OSV: https://osv.dev/vulnerability/CVE-2023-41897

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-41897/
Summaries are generated and may contain mistakes; the official description above is the record.