dbcve.org
Home Assistant CompanionApplication · Home Assistant

CVE-2023-44385

HIGH · 8.8 CVSS v3.1 Published 2023-10-19
Fix available
A fix is available. Upgrade to 2023.7 or later.
See remediation →
95/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
The Home Assistant Companion for iOS and macOS app up to version 2023.4 are vulnerable to Client-Side Request Forgery. Attackers may send malicious links/QRs to victims that, when visited, will make the victim to call arbitrary services in their Home Assistant installation. Combined with this security advisory, may result in full compromise and remote code execution (RCE). Version 2023.7 addresses this issue and all users are advised to upgrade. There are no known workarounds for this vulnerability. This issue is also tracked as GitHub Security Lab (GHSL) Vulnerability Report: GHSL-2023-161.

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

The Home Assistant Companion iOS/macOS app before version 2023.4 contained a Client-Side Request Forgery (CSRF) vulnerability. Attackers could send malicious links or QR codes that, when opened by victims, would cause the victim's app to make arbitrary service calls to their Home Assistant instance. This can lead to full compromise and RCE when chained with other vulnerabilities.

MitigationUpgrade the Home Assistant Companion for iOS and macOS to version 2023.7 or later. There are no available workarounds; the only remediation is applying the vendor patch.

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 Assistant CompanionApplication
Affected:< 2023.7

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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. Identify the installed app version on iOS
    Open the App Store, tap your profile icon, scroll to 'Purchased' > 'My Purchases', find Home Assistant Companion, and note the version number shown. Alternatively, check in the app's listing page in the App Store.
    Affected if The displayed version is lower than 2023.7 (e.g., 2023.6.x or earlier)
  2. Identify the installed app version on macOS
    Open the Mac App Store, click your profile picture, find Home Assistant Companion in the purchased list, and note the version number. Alternatively, right-click the app in Applications and select 'Get Info' to view the version.
    Affected if The displayed version is lower than 2023.7 (e.g., 2023.6.x or earlier)
  3. Verify the app connection status
    Open the Home Assistant Companion app and confirm whether it shows as connected to a Home Assistant instance (the app must be connected to a server for the CSRF flaw to be exploitable).
    Affected if The app is connected to a Home Assistant server AND the app version is below 2023.7
  4. Check for recent app updates
    Navigate to the App Store (iOS/macOS) updates section and search for Home Assistant Companion to see if an update to version 2023.7 or later is available or has been applied.
    Affected if The update to version 2023.7 or later has not been installed

You are affected if the Home Assistant Companion app version is below 2023.7 and the app is connected or has ever been connected to a Home Assistant instance.

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.7 or later
Fixed in 2023.7
Interim mitigation

Upgrade the Home Assistant Companion for iOS and macOS to version 2023.7 or later. There are no available workarounds; the only remediation is applying the vendor patch.

Recommended fix High confidence

2023.7 or later

  1. Open the App Store (iOS) or Mac App Store (macOS) on your device
  2. Search for 'Home Assistant Companion'
  3. Locate the Home Assistant Companion app in the search results
  4. Tap or click the Update button to install version 2023.7 or later
  5. Verify the updated version number in the app after updating

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

Fix this in Home Assistant Companion Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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