Approved changes feed: RSS · Atom

cpe:2.3:a:eclipse:edc_connector:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorEclipse (fa988180-604e-5c1f-93ea-65b5297000fc)
ProductEdc Connector (90a7f969-4126-54bc-8612-92f9ca797ef9)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/eclipse-edc/connector purl2cpe 2026-06-01 10:15:03.591299

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-4536 vulnerable 2026-06-03 14:57:15.710893 Eclipse EDC: OAuth2 Credential Exfiltration Vulnerability
MEDIUM (6.8)
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.
Published: 2024-05-07T13:11:45.310Z
Updated: 2024-08-01T20:40:47.492Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.