dbcve.org
Home AssistantApplication

CVE-2023-27482

CRITICAL · 10.0 CVSS v3.1 Published 2023-03-08
Fix available
A fix is available. Upgrade to 2023.3.0 / 2023.03.1 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
homeassistant is an open source home automation tool. A remotely exploitable vulnerability bypassing authentication for accessing the Supervisor API through Home Assistant has been discovered. This impacts all Home Assistant installation types that use the Supervisor 2023.01.1 or older. Installation types, like Home Assistant Container (for example Docker), or Home Assistant Core manually in a Python environment, are not affected. The issue has been mitigated and closed in Supervisor version 2023.03.1, which has been rolled out to all affected installations via the auto-update feature of the Supervisor. This rollout has been completed at the time of publication of this advisory. Home Assistant Core 2023.3.0 included mitigation for this vulnerability. Upgrading to at least that version is thus advised. In case one is not able to upgrade the Home Assistant Supervisor or the Home Assistant Core application at this time, it is advised to not expose your Home Assistant instance to the internet.

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

This is an authentication bypass vulnerability in the Home Assistant Supervisor API that allows remote attackers to bypass authentication and access the Supervisor API without credentials. It affects all Home Assistant installations using Supervisor version 2023.01.1 or older, but does not affect Container (Docker) or manually installed Core environments.

MitigationUpgrade to Home Assistant Supervisor version 2023.03.1 or later, or Home Assistant Core 2023.3.0 or later. If unable to upgrade immediately, ensure the Home Assistant instance is not exposed to the internet.

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.3.0
SupervisorApplication
Affected:< 2023.03.1

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Verify you are using Home Assistant Supervisor
    Check your installation type. In Home Assistant, go to Settings > System > About and look for 'Supervisor' in the system health information. If you see Supervisor listed, you are using the affected installation method. Alternatively, HA OS and Supervised installations have Supervisor, while Container (Docker) or core-only installs do not.
    Affected if The system shows Supervisor is present - this means you are using the affected installation type.
  2. Check your Home Assistant Core version
    In the Home Assistant UI, go to Settings > System > About. The Core version is displayed on that page. Compare it to the affected range: any version before 2023.3.0 is vulnerable.
    Affected if The installed Core version is 2023.2.x or earlier.
  3. Check your Supervisor version
    In the Home Assistant UI, go to Settings > System > Supervisor. The Supervisor version is shown on that page. Compare it to 2023.03.1 - any version before 2023.03.1 is vulnerable.
    Affected if The installed Supervisor version is 2023.01.1 or older.
  4. Verify the Supervisor API is accessible
    The vulnerability exists in the Supervisor API endpoint. Check your router/firewall to determine if port 4357 (the Supervisor port) or the Home Assistant instance is exposed to the internet. Even on local networks, any unauthorized access to the Supervisor API could exploit this flaw.
    Affected if The Supervisor API (port 4357) or your Home Assistant instance is reachable from untrusted networks.

You are affected if you are using Home Assistant with Supervisor (HA OS or Supervised install), and either your Core version is below 2023.3.0 or your Supervisor version is below 2023.03.1.

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.3.0 / 2023.03.1 or later
Fixed in 2023.3.02023.03.1
Interim mitigation

Upgrade to Home Assistant Supervisor version 2023.03.1 or later, or Home Assistant Core 2023.3.0 or later. If unable to upgrade immediately, ensure the Home Assistant instance is not exposed to the internet.

Recommended fix High confidence

Home Assistant Core 2023.3.0 or later / Supervisor 2023.03.1 or later

  1. Check your current Home Assistant Core version and Supervisor version in the Home Assistant UI (Settings > System > Repairs > three dots > System information)
  2. If running Home Assistant Core with Supervisor, ensure Supervisor auto-update has applied version 2023.03.1 or later
  3. Alternatively, upgrade Home Assistant Core to version 2023.3.0 or later which includes the mitigation
  4. Verify the update was successful by checking the version again in System information
  5. If unable to upgrade, ensure your Home Assistant instance is not exposed to the internet (disable any port forwarding or use a VPN for remote access)

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-27482 — 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-27482 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