{"id":"CVE-2025-25305","state":"PUBLISHED","title":"SSL validation for outgoing requests in Home Assistant Core and used libs not correct","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.","publishedAt":"2025-02-18T18:53:10.870Z","updatedAt":"2025-02-18T19:23:41.622Z","severity":{"score":7,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L","source":"GitHub_M"},"assigner":"GitHub_M","products":["home-assistant core"],"affected":[{"vendor":"home-assistant","product":"core","versions":[{"version":"< 2024.1.6","status":"affected"}]}],"references":["https://github.com/home-assistant/core/security/advisories/GHSA-m3pm-rpgg-5wj6"],"weaknesses":["CWE-940"],"ingestedAt":"2026-10-29T20:08:47.682Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2025/25xxx/CVE-2025-25305.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.1","cveMetadata":{"cveId":"CVE-2025-25305","state":"PUBLISHED","datePublished":"2025-02-18T18:53:10.870Z","dateUpdated":"2025-02-18T19:23:41.622Z","assignerShortName":"GitHub_M","assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","dateReserved":"2025-02-06T17:13:33.124Z"},"containers":{"cna":{"title":"SSL validation for outgoing requests in Home Assistant Core and used libs not correct","descriptions":[{"lang":"en","value":"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."}],"affected":[{"vendor":"home-assistant","product":"core","versions":[{"version":"< 2024.1.6","status":"affected"}]}],"references":[{"url":"https://github.com/home-assistant/core/security/advisories/GHSA-m3pm-rpgg-5wj6","name":"https://github.com/home-assistant/core/security/advisories/GHSA-m3pm-rpgg-5wj6","tags":["x_refsource_CONFIRM"]}],"metrics":[{"cvssV3_1":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"LOW","baseScore":7,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"LOW","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-940","lang":"en","description":"CWE-940: Improper Verification of Source of a Communication Channel","type":"CWE"}]}],"providerMetadata":{"shortName":"GitHub_M","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","dateUpdated":"2025-02-18T18:53:10.870Z"},"source":{"advisory":"GHSA-m3pm-rpgg-5wj6","discovery":"UNKNOWN"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2025-02-18T19:23:18.464411Z","id":"CVE-2025-25305","options":[{"Exploitation":"poc"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2025-02-18T19:23:41.622Z"}}]}}}