CVE-2025-55192

{"id": "CVE-2025-55192", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.6, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "LOW", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2025-08-14T17:15:41.173", "references": [{"url": "https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/commit/2a3b80ff128ddf4f410c97dd47a94343792ce43c", "source": "security-advisories@github.com"}, {"url": "https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/security/advisories/GHSA-xccg-43hx-c846", "source": "security-advisories@github.com"}, {"url": "https://securitylab.github.com/advisories/GHSL-2025-101_homeassistant-tapo-control", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-94"}]}], "descriptions": [{"lang": "en", "value": "HomeAssistant-Tapo-Control offers Control for Tapo cameras as a Home Assistant component. Prior to commit 2a3b80f, there is a code injection vulnerability in the GitHub Actions workflow .github/workflows/issues.yml. It does not affect users of the Home Assistant integration itself \u2014 it only impacts the GitHub Actions environment for this repository. The vulnerable workflow directly inserted user-controlled content from the issue body (github.event.issue.body) into a Bash conditional without proper sanitization. A malicious GitHub user could craft an issue body that executes arbitrary commands on the GitHub Actions runner in a privileged context whenever an issue is opened. The potential impact is limited to the repository\u2019s CI/CD environment, which could allow access to repository contents or GitHub Actions secrets. This issue has been patched via commit 2a3b80f. Workarounds involve disabling the affected workflow (issues.yml), replacing the unsafe Bash comparison with a safe quoted grep (or a pure GitHub Actions expression check), or ensuring minimal permissions in workflows (permissions: block) to reduce possible impact."}, {"lang": "es", "value": "HomeAssistant-Tapo-Control ofrece control para c\u00e1maras Tapo como componente de Home Assistant. Antes de el commit 2a3b80f, exist\u00eda una vulnerabilidad de inyecci\u00f3n de c\u00f3digo en el flujo de trabajo de GitHub Actions .github/workflows/issues.yml. Esta vulnerabilidad no afecta a los usuarios de la integraci\u00f3n de Home Assistant, sino solo al entorno de GitHub Actions de este repositorio. El flujo de trabajo vulnerable insertaba directamente contenido controlado por el usuario del cuerpo de la incidencia (github.event.issue.body) en una condici\u00f3n de Bash sin la debida depuraci\u00f3n. Un usuario malintencionado de GitHub podr\u00eda manipular un cuerpo de incidencia que ejecute comandos arbitrarios en el ejecutor de GitHub Actions en un contexto privilegiado al abrir una incidencia. El impacto potencial se limita al entorno de CI/CD del repositorio, lo que podr\u00eda permitir el acceso al contenido del repositorio o a los secretos de GitHub Actions. Este problema se ha corregido mediante el commit 2a3b80f. Las soluciones alternativas implican deshabilitar el flujo de trabajo afectado (issues.yml), reemplazar la comparaci\u00f3n insegura de Bash con un grep entre comillas seguro (o una verificaci\u00f3n de expresi\u00f3n de GitHub Actions pura) o garantizar permisos m\u00ednimos en los flujos de trabajo (bloque de permisos:) para reducir el posible impacto."}], "lastModified": "2025-09-12T19:15:33.630", "sourceIdentifier": "security-advisories@github.com"}