CVE-2024-4536

Eclipse EDC: OAuth2 Credential Exfiltration Vulnerability

Published May 7, 2024 CVSS 3.1 · 6.8 Medium EPSS < 1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2024-1371 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.
Github GHSA Github GHSA GHSA-2x52-8f29-7cjr Eclipse Dataspace Components vulnerable to OAuth2 client secret disclosure
History
Type Values Removed Values Added
First Time appeared Eclipse
Eclipse edc Connector
CPEs cpe:2.3:a:eclipse:edc_connector:*:*:*:*:*:*:*:*
Vendors & Products Eclipse
Eclipse edc Connector
Weaknesses

Sources

Status
PUBLISHED
Assigner
eclipse
Published
Updated
Aug 1, 2024, 8:40 PM
Reserved
May 6, 2024, 7:05 AM
Status
Analyzed
Published
May 7, 2024, 1:15 PM
Modified
Jun 17, 2026, 8:02 AM