CVE-2024-4536

{"id": "CVE-2024-4536", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "emo@eclipse.org", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 6.8, "attackVector": "ADJACENT_NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "LOW", "privilegesRequired": "HIGH", "confidentialityImpact": "HIGH"}, "impactScore": 5.3, "exploitabilityScore": 1.0}]}, "published": "2024-05-07T13:15:48.513", "references": [{"url": "https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b", "source": "emo@eclipse.org"}, {"url": "https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3", "source": "emo@eclipse.org"}, {"url": "https://gitlab.eclipse.org/security/cve-assignement/-/issues/22", "source": "emo@eclipse.org"}, {"url": "https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198", "source": "emo@eclipse.org"}, {"url": "https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://gitlab.eclipse.org/security/cve-assignement/-/issues/22", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "emo@eclipse.org", "description": [{"lang": "en", "value": "CWE-201"}, {"lang": "en", "value": "CWE-522"}]}], "descriptions": [{"lang": "en", "value": "In Eclipse Dataspace Components from version 0.2.1 to 0.6.2, in the EDC Connector component ( https://github.com/eclipse-edc/Connector ), an attacker might obtain OAuth2 client secrets from the vault.\n\nIn Eclipse Dataspace Components from version 0.2.1 to 0.6.2, we have identified a security vulnerability in the EDC Connector component ( https://github.com/eclipse-edc/Connector ) regarding the OAuth2-protected data sink feature. When using a custom, OAuth2-protected data sink, the OAuth2-specific data address properties are resolved by the provider data plane. Problematically, the consumer-provided clientSecretKey, which indicates the OAuth2 client secret to retrieve from a secrets vault, is resolved in the context of the provider's vault, not the consumer. This secret's value is then sent to the tokenUrl, also consumer-controlled, as part of an OAuth2 client credentials grant. The returned access token is then sent as a bearer token to the data sink URL.\n\nThis feature is now disabled entirely, because not all code paths necessary for a successful realization were fully implemented.\n\n"}, {"lang": "es", "value": "En los componentes de Eclipse Dataspace de la versi\u00f3n 0.2.1 a 0.6.2, en el componente EDC Connector (https://github.com/eclipse-edc/Connector), un atacante podr\u00eda obtener secretos del cliente OAuth2 de la b\u00f3veda. En los componentes de Eclipse Dataspace de la versi\u00f3n 0.2.1 a 0.6.2, hemos identificado una vulnerabilidad de seguridad en el componente EDC Connector (https://github.com/eclipse-edc/Connector) con respecto a la funci\u00f3n de receptor de datos protegido por OAuth2. Cuando se utiliza un receptor de datos personalizado protegido por OAuth2, el plano de datos del proveedor resuelve las propiedades de direcci\u00f3n de datos espec\u00edficas de OAuth2. Lo problem\u00e1tico es que la clientSecretKey proporcionada por el consumidor, que indica el secreto del cliente OAuth2 para recuperar de una b\u00f3veda de secretos, se resuelve en el contexto de la b\u00f3veda del proveedor, no en el del consumidor. Luego, el valor de este secreto se env\u00eda a tokenUrl, tambi\u00e9n controlado por el consumidor, como parte de una concesi\u00f3n de credenciales de cliente OAuth2. El token de acceso devuelto se env\u00eda luego como token de portador a la URL del receptor de datos. Esta caracter\u00edstica ahora est\u00e1 completamente deshabilitada porque no se implementaron completamente todas las rutas de c\u00f3digo necesarias para una realizaci\u00f3n exitosa."}], "lastModified": "2024-11-21T09:43:03.563", "sourceIdentifier": "emo@eclipse.org"}