dbcve.org
Home AssistantApplication

CVE-2023-41897

CRITICAL · 9.6 CVSS v3.1 Published 2023-10-19
Fix available
A fix is available. Upgrade to 2023.9.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Home Assistant server fails to set HTTP security headers, specifically X-Frame-Options, allowing attackers to embed the application in an invisible frame. This enables clickjacking attacks where users are tricked into interacting with hidden elements, such as approving malicious add-on installations that lead to Remote Code Execution.

MitigationUpgrade to Home Assistant version 2023.9.0 or later, which implements proper HTTP security headers including X-Frame-Options.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Home AssistantApplication
Affected:< 2023.9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Home Assistant version
    Log in to the Home Assistant web interface and navigate to Settings > System > About, or check the version via CLI using 'ha core info' if you have the Home Assistant CLI access, or inspect the version from the frontend response.
    Affected if The displayed version is lower than 2023.9.0 (e.g., 2023.8.x, 2023.7.x, etc.)
  2. Inspect HTTP response headers for X-Frame-Options
    Use a browser developer tool (Network tab) or a command-line tool like curl: 'curl -I https://your-home-assistant-url' and examine the response headers.
    Affected if The X-Frame-Options header is missing from the HTTP response, or the header value is not set to 'DENY' or 'SAMEORIGIN'.
  3. Verify if the Home Assistant UI can be embedded in a frame
    Create a simple HTML test page with an iframe pointing to your Home Assistant URL (e.g., <iframe src="https://YOUR-HA-URL"></iframe>) and open it in a browser. Check if the content loads inside the frame.
    Affected if The Home Assistant interface loads successfully inside a third-party iframe without being blocked by the browser.
  4. Check for Content-Security-Policy header
    Use curl or browser dev tools to inspect response headers for the Content-Security-Policy header, specifically looking for frame-ancestors directive.
    Affected if The Content-Security-Policy header is missing or does not include frame-ancestors directive restricting framing.

You are affected if your Home Assistant version is below 2023.9.0 AND the HTTP responses lack X-Frame-Options or proper Content-Security-Policy frame-ancestors restrictions, allowing your instance to be embedded in iframes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2023.9.0 or later
Fixed in 2023.9.0
Interim mitigation

Upgrade to Home Assistant version 2023.9.0 or later, which implements proper HTTP security headers including X-Frame-Options.

Recommended fix High confidence

Home Assistant 2023.9.0 or later

  1. Ensure you have a backup of your Home Assistant configuration
  2. Access your Home Assistant instance
  3. Navigate to Settings > System > Updates (or use the Supervisor panel in older setups)
  4. Click 'Update' to install the latest version
  5. Verify the update completes successfully and Home Assistant restarts
  6. Confirm the installation is running version 2023.9.0 or later
Caveat No breaking changes mentioned in the security advisory

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Home Assistant Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41897 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-41897 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data