dbcve.org
Home AssistantApplication

CVE-2023-41899

HIGH · 7.2 CVSS v3.1 Published 2023-10-19
Fix available
A fix is available. Upgrade to 2023.9.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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. In affected versions the `hassio.addon_stdin` is vulnerable to a partial Server-Side Request Forgery where an attacker capable of calling this service (e.g.: through GHSA-h2jp-7grc-9xpp) may be able to invoke any Supervisor REST API endpoints with a POST request. An attacker able to exploit will be able to control the data dictionary, including its addon and input key/values. 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. This issue is also tracked as GitHub Security Lab (GHSL) Vulnerability Report: `GHSL-2023-162`.

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's `hassio.addon_stdin` service contains a partial Server-Side Request Forgery (SSRF) vulnerability. An attacker who can call this service (requires prior access via GHSL-2023-162) can send POST requests to arbitrary Supervisor REST API endpoints and control the data dictionary including addon and input key/value parameters.

MitigationUpgrade Home Assistant to version 2023.9.0 or later. No workarounds exist; the vulnerable service must be patched via the version upgrade.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 installed Home Assistant version
    In the Home Assistant UI, go to Settings > System > Info, or check the homeassistant.version file in the config directory. Alternatively, call the Home Assistant API at /api/discovery_info or check the supervisor's homeassistant info via 'ha core info' command.
    Affected if The installed version is any version prior to 2023.9.0 (e.g., 2023.8.x, 2023.7.x, earlier releases).
  2. Confirm hassio.addon_stdin service exists
    In the Home Assistant UI, go to Developer Tools > Services and search for 'hassio.addon_stdin' service, or query the Home Assistant API endpoint /api/services to list all available services.
    Affected if The 'hassio.addon_stdin' service appears in the available services list, meaning it is enabled and callable.
  3. Check access to hassio.addgerstdin service
    Review Home Assistant's authentication and authorization configuration to determine what privileges are required to call the hassio.addon_stdin service. An attacker with authenticated access (even limited) to call this service could exploit the SSRF.
    Affected if The hassio.addon_stdin service can be invoked by an authenticated user who has obtained prior access (such as via GHSL-2023-162), indicating the vulnerability is exploitable in the current setup.

You are affected if your Home Assistant version is before 2023.9.0 AND the hassio.addon_stdin service is available and callable by an attacker who has obtained initial access to your 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.9.0 or later
Fixed in 2023.9.0
Interim mitigation

Upgrade Home Assistant to version 2023.9.0 or later. No workarounds exist; the vulnerable service must be patched via the version upgrade.

Recommended fix High confidence

Home Assistant 2023.9.0

  1. 1. Back up your Home Assistant configuration (including configuration.yaml, automations, and any custom integrations)
  2. 2. Check your current Home Assistant version in Settings > System > About
  3. 3. Upgrade Home Assistant to version 2023.9.0 or later using your preferred installation method (e.g., Home Assistant OS: Settings > System > Repositories > Check for updates, or via pip: pip install --upgrade homeassistant)
  4. 4. After upgrade completes, verify the version shows 2023.9.0 or higher in Settings > System > About
  5. 5. Test that your automations and integrations are functioning correctly
  6. 6. If using the Supervisor, ensure the add-on updates are applied as well
Caveat Review the Home Assistant 2023.9.0 release notes for potential breaking changes in your automations, custom components, or integrations before upgrading

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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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