CVE-2025-55196

{"id": "CVE-2025-55196", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 7.1, "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:N/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": "NONE", "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-13T23:15:27.500", "references": [{"url": "https://github.com/external-secrets/external-secrets/commit/39cdba5863533007b582dc63dd300839326b2f1d", "source": "security-advisories@github.com"}, {"url": "https://github.com/external-secrets/external-secrets/commit/de40e8f4fa9559c1d770bb674589b285da5ef2d1", "source": "security-advisories@github.com"}, {"url": "https://github.com/external-secrets/external-secrets/pull/5109", "source": "security-advisories@github.com"}, {"url": "https://github.com/external-secrets/external-secrets/pull/5133", "source": "security-advisories@github.com"}, {"url": "https://github.com/external-secrets/external-secrets/security/advisories/GHSA-fcxq-v2r3-cc8h", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-284"}]}], "descriptions": [{"lang": "en", "value": "External Secrets Operator is a Kubernetes operator that integrates external secret management systems. From version 0.15.0 to before 0.19.2, a vulnerability was discovered where the List() calls for Kubernetes Secret and SecretStore resources performed by the PushSecret controller did not apply a namespace selector. This flaw allowed an attacker to use label selectors to list and read secrets/secret-stores across the cluster, bypassing intended namespace restrictions. An attacker with the ability to create or update PushSecret resources and control SecretStore configurations could exploit this vulnerability to exfiltrate sensitive data from arbitrary namespaces. This could lead to full disclosure of Kubernetes secrets, including credentials, tokens, and other sensitive information stored in the cluster. This vulnerability has been patched in version 0.19.2. A workaround for this issue includes auditing and restricting RBAC permissions so that only trusted service accounts can create or update PushSecret and SecretStore resources."}, {"lang": "es", "value": "External Secrets Operator de Kubernetes que integra sistemas externos de gesti\u00f3n de secretos. Desde la versi\u00f3n 0.15.0 hasta la 0.19.2, se descubri\u00f3 una vulnerabilidad en la que las llamadas List() para los recursos Secret y SecretStore de Kubernetes, realizadas por el controlador PushSecret, no aplicaban un selector de espacio de nombres. Esta falla permit\u00eda a un atacante usar selectores de etiquetas para listar y leer secretos y almacenes de secretos en el cl\u00faster, eludiendo las restricciones de espacio de nombres previstas. Un atacante con la capacidad de crear o actualizar recursos PushSecret y controlar las configuraciones de SecretStore podr\u00eda explotar esta vulnerabilidad para extraer datos confidenciales de espacios de nombres arbitrarios. Esto podr\u00eda provocar la divulgaci\u00f3n completa de secretos de Kubernetes, incluyendo credenciales, tokens y otra informaci\u00f3n confidencial almacenada en el cl\u00faster. Esta vulnerabilidad se ha corregido en la versi\u00f3n 0.19.2. Una soluci\u00f3n alternativa para este problema incluye auditar y restringir los permisos RBAC para que solo las cuentas de servicio de confianza puedan crear o actualizar recursos PushSecret y SecretStore."}], "lastModified": "2025-08-14T13:11:53.633", "sourceIdentifier": "security-advisories@github.com"}