CVE-2024-4536
Assigner: eclipse
Published: 2024-05-07T13:11:45.310Z
State: PUBLISHED
affected: defaultStatus: unaffected
modules: Connector
packageName: technology.edc
product: EDC
repo: https://github.com/eclipse-edc/Connector
vendor: Eclipse Foundation
versions: lessThanOrEqual: 0.6.2
status: affected
version: 0.2.1
versionType: semver
credits: type: finder
value: sovity GmbH
descriptions: supportingMedia: base64: no
type: text/html
value: <div>In Eclipse Dataspace Components from version 0.2.1 to 0.6.2, in the EDC Connector component (<a target="_blank" rel="nofollow" href="https://github.com/eclipse-edc/Connector">https://github.com/eclipse-edc/Connector</a>), an attacker might obtain OAuth2 client secrets from the vault.</div><div><br></div><div><p>In Eclipse Dataspace Components from version 0.2.1 to 0.6.2, we have identified a security vulnerability in the EDC Connector component (<a target="_blank" rel="nofollow" href="https://github.com/eclipse-edc/Connector">https://github.com/eclipse-edc/Connector</a>) 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.</p>
<p>This feature is now disabled entirely, because not all code paths necessary for a successful realization were fully implemented.</p><br></div><br>
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.

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.


metrics: cvssV3_1: attackComplexity: HIGH
attackVector: ADJACENT_NETWORK
availabilityImpact: LOW
baseScore: 6.8
baseSeverity: MEDIUM
confidentialityImpact: HIGH
integrityImpact: LOW
privilegesRequired: HIGH
scope: CHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L
version: 3.1
format: CVSS
scenarios: value: GENERAL
problemTypes: descriptions: cweId: CWE-201
description: CWE-201: Insertion of Sensitive Information Into Sent Data
type: CWE
descriptions: cweId: CWE-522
description: CWE-522: Insufficiently Protected Credentials
type: CWE
source: discovery: UNKNOWN
title: Eclipse EDC: OAuth2 Credential Exfiltration Vulnerability
x_generator: engine: Vulnogram 0.1.0-dev