CVE-2023-41896

{"id": "CVE-2023-41896", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 1.2}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 9.0, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 2.3}]}, "published": "2023-10-19T23:15:08.540", "references": [{"url": "https://github.com/home-assistant/core/security/advisories/GHSA-935v-rmg9-44mw", "tags": ["Not Applicable"], "source": "security-advisories@github.com"}, {"url": "https://github.com/home-assistant/core/security/advisories/GHSA-cr83-q7r2-7f5q", "tags": ["Vendor Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/home-assistant/core/security/advisories/GHSA-935v-rmg9-44mw", "tags": ["Not Applicable"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/home-assistant/core/security/advisories/GHSA-cr83-q7r2-7f5q", "tags": ["Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-345"}]}, {"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-345"}]}], "descriptions": [{"lang": "en", "value": "Home assistant is an open source home automation. Whilst auditing the frontend code to identify hidden parameters, Cure53 detected `auth_callback=1`, which is leveraged by the WebSocket authentication logic in tandem with the `state` parameter. The state parameter contains the `hassUrl`, which is subsequently utilized to establish a WebSocket connection. This behavior permits an attacker to create a malicious Home Assistant link with a modified state parameter that forces the frontend to connect to an alternative WebSocket backend. Henceforth, the attacker can spoof any WebSocket responses and trigger cross site scripting (XSS). Since the XSS is executed on the actual Home Assistant frontend domain, it can connect to the real Home Assistant backend, which essentially represents a comprehensive takeover scenario. Permitting the site to be iframed by other origins, as discussed in GHSA-935v-rmg9-44mw, renders this exploit substantially covert since a malicious website can obfuscate the compromise strategy in the background. However, even without this, the attacker can still send the `auth_callback` link directly to the victim user. To mitigate this issue, Cure53 advises modifying the WebSocket code\u2019s authentication flow. An optimal implementation in this regard would not trust the `hassUrl` passed in by a GET parameter. Cure53 must stipulate the significant time required of the Cure53 consultants to identify an XSS vector, despite holding full control over the WebSocket responses. In many areas, data from the WebSocket was properly sanitized, which hinders post-exploitation. The audit team eventually detected the `js_url` for custom panels, though generally, the frontend exhibited reasonable security hardening. This issue has been addressed in Home Assistant Core version 2023.8.0 and in the npm package home-assistant-js-websocket in version 8.2.0. Users are advised to upgrade. There are no known workarounds for this vulnerability."}, {"lang": "es", "value": "Home Assistant es una dom\u00f3tica de c\u00f3digo abierto. Mientras auditaba el c\u00f3digo de la interfaz para identificar par\u00e1metros ocultos, Cure53 detect\u00f3 `auth_callback=1`, que es aprovechado por la l\u00f3gica de autenticaci\u00f3n de WebSocket junto con el par\u00e1metro `state`. El par\u00e1metro de estado contiene `hassUrl`, que posteriormente se utiliza para establecer una conexi\u00f3n WebSocket. Este comportamiento permite a un atacante crear un enlace malicioso de Home Assistant con un par\u00e1metro de estado modificado que obliga al frontend a conectarse a un backend WebSocket alternativo. De ahora en adelante, el atacante puede falsificar cualquier respuesta de WebSocket y activar Cross-Site Scripting (XSS). Dado que XSS se ejecuta en el dominio frontend real de Home Assistant, puede conectarse al backend real de Home Assistant, lo que esencialmente representa un escenario de adquisici\u00f3n integral. Permitir que el sitio tenga un iframe de otros or\u00edgenes, como se analiza en GHSA-935v-rmg9-44mw, hace que este exploit sea sustancialmente encubierto, ya que un sitio web malicioso puede ofuscar la estrategia de compromiso en segundo plano. Sin embargo, incluso sin esto, el atacante a\u00fan puede enviar el enlace `auth_callback` directamente al usuario v\u00edctima. Para mitigar este problema, Cure53 recomienda modificar el flujo de autenticaci\u00f3n del c\u00f3digo WebSocket. Una implementaci\u00f3n \u00f3ptima a este respecto no confiar\u00eda en el `hassUrl` pasado por un par\u00e1metro GET. Cure53 debe estipular el importante tiempo requerido por los consultores de Cure53 para identificar un vector XSS, a pesar de tener control total sobre las respuestas de WebSocket. En muchas \u00e1reas, los datos del WebSocket se sanitizaron adecuadamente, lo que dificulta su posterior explotaci\u00f3n. El equipo de auditor\u00eda finalmente detect\u00f3 el `js_url` para paneles personalizados, aunque en general, la interfaz mostr\u00f3 un refuerzo de seguridad razonable. Este problema se solucion\u00f3 en la versi\u00f3n 2023.8.0 de Home Assistant Core y en el paquete npm home-assistant-js-websocket en la versi\u00f3n 8.2.0. Se recomienda a los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad."}], "lastModified": "2024-11-21T08:21:52.620", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:home-assistant:home-assistant:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "5FA5180B-1B8F-4CF6-84F2-A41078BC5BF9", "versionEndExcluding": "2023.8.0"}, {"criteria": "cpe:2.3:a:home-assistant:home-assistant-js-websocket:*:*:*:*:*:node.js:*:*", "vulnerable": true, "matchCriteriaId": "08A4163A-BF4B-4823-ADB6-81078E9345F5", "versionEndExcluding": "8.2.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}