dbcve.org
Home AssistantApplication

CVE-2023-41894

MEDIUM · 5.3 CVSS v3.1 Published 2023-10-20
Fix available
A fix is available. Upgrade to 2023.9.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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. The assessment verified that webhooks available in the webhook component are triggerable via the `*.ui.nabu.casa` URL without authentication, even when the webhook is marked as Only accessible from the local network. This issue is facilitated by the SniTun proxy, which sets the source address to 127.0.0.1 on all requests sent to the public URL and forwarded to the local Home Assistant. 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

Webhooks in Home Assistant marked as 'Only accessible from the local network' can be triggered remotely without authentication via the cloud URL (*.ui.nabu.casa). The SniTun proxy incorrectly spoofs all requests as originating from 127.0.0.1, bypassing the local network access control that is meant to restrict these webhooks.

MitigationUpgrade to Home Assistant version 2023.9.0 or later. There are no known workarounds.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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. Check your Home Assistant version
    Navigate to Settings > System > Info in the Home Assistant UI, or check the version displayed on the welcome page
    Affected if The installed version is before 2023.9.0 (e.g., 2023.8.x, 2023.7.x, etc.)
  2. Verify if Nabu Casa cloud is connected
    Navigate to Settings > Voice assistants > Home Assistant Cloud in the UI, or check for the cloud connection status icon in the sidebar
    Affected if Cloud connection is active and *.ui.nabu.casa URLs are accessible
  3. Identify webhooks with local-only access
    Navigate to Settings > Automations & Scenes > Webhooks (or search for webhook integrations), review each webhook configuration for the 'Only accessible from the local network' setting
    Affected if Any webhook is configured with the 'Only accessible from the local network' option enabled
  4. Confirm webhooks can be accessed via cloud URL
    Attempt to access a local-only webhook via its *.ui.nabu.casa URL from an external network (not on the same LAN)
    Affected if The webhook responds successfully when accessed through the cloud URL, bypassing the local network restriction

You are affected if running Home Assistant version before 2023.9.0 with cloud enabled and any webhooks configured as 'Only accessible from the local network' can be triggered via the cloud URL.

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. There are no known workarounds.

Recommended fix High confidence

2023.9.0

  1. Upgrade Home Assistant to version 2023.9.0 or later
  2. To upgrade, use your Home Assistant's dashboard: go to Settings > System > Repositories, or use the CLI: ha core update --version 2023.9.0
  3. Alternatively, reinstall Home Assistant with the 2023.9.0 or newer image

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

Fix this in Home Assistant Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41894 — 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-41894 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