CVE-2024-4536 – org.eclipse.edc:connector-core

Package

Manager: maven
Name: org.eclipse.edc:connector-core
Vulnerable Version: >=0.2.1 <0.6.3

Severity

Level: Medium

CVSS v3.1: CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L

CVSS v4.0: CVSS:4.0/AV:A/AC:H/AT:N/PR:H/UI:N/VC:H/VI:L/VA:L/SC:H/SI:L/SA:L

EPSS: 0.00034 pctl0.08162

Details

Eclipse Dataspace Components vulnerable to OAuth2 client secret disclosure 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. In 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. This feature is now disabled entirely, because not all code paths necessary for a successful realization were fully implemented.

Metadata

Created: 2024-05-07T15:30:36Z
Modified: 2025-02-06T19:33:44Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/05/GHSA-2x52-8f29-7cjr/GHSA-2x52-8f29-7cjr.json
CWE IDs: ["CWE-201", "CWE-522"]
Alternative ID: GHSA-2x52-8f29-7cjr
Finding: F038
Auto approve: 1