logo_clicknbuy.png

CVE-2025-25305 – Home Assistant Core SSL Verification Bypass

The following table lists the changes that have been made to the
CVE-2025-25305 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution
of a vulnerability, and for identifying the most recent changes that may
impact the vulnerability’s severity, exploitability, or other characteristics.

  • New CVE Received
    by [email protected]

    Feb. 18, 2025

    Action Type Old Value New Value
    Added Description Home Assistant Core is an open source home automation that puts local control and privacy first. Affected versions are subject to a potential man-in-the-middle attacks due to missing SSL certificate verification in the project codebase and used third-party libraries. In the past, `aiohttp-session`/`request` had the parameter `verify_ssl` to control SSL certificate verification. This was a boolean value. In `aiohttp` 3.0, this parameter was deprecated in favor of the `ssl` parameter. Only when `ssl` is set to `None` or provided with a correct configured SSL context the standard SSL certificate verification will happen. When migrating integrations in Home Assistant and libraries used by Home Assistant, in some cases the `verify_ssl` parameter value was just moved to the new `ssl` parameter. This resulted in these integrations and 3rd party libraries using `request.ssl = True`, which unintentionally turned off SSL certificate verification and opened up a man-in-the-middle attack vector. This issue has been addressed in version 2024.1.6 and all users are advised to upgrade. There are no known workarounds for this vulnerability.
    Added CVSS V3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L
    Added CWE CWE-940
    Added Reference https://github.com/home-assistant/core/security/advisories/GHSA-m3pm-rpgg-5wj6
Share the Post:

Related Posts