CVE-2024-4536 json
Eclipse EDC: OAuth2 Credential Exfiltration Vulnerability
published 2024-05-07 2 y ago modified 2026-06-17 4 mo ago also GHSA-2x52-8f29-7cjr , EUVD-2024-1371
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.eclipse.edc:connector-core 0.6.3
- eclipse edc_connector 0.6.3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:L |
| GitHub | 3.1 | 6.8 | CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.eclipse.edc:connector-core | >=0.2.1, <0.6.3 |
0.6.3 |
Affected products
- Eclipse Foundation EDC
- eclipse_foundation edc
Classification
References
-
github.com
/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b
patch, web
-
gitlab.eclipse.org
/security/cve-assignement/-/issues/22
issue-tracking, vendor-advisory, web
-
gitlab.eclipse.org
/security/vulnerability-reports/-/issues/198
issue-tracking, vendor-advisory, web
-
github.com
/eclipse-edc/Connector/releases/tag/v0.6.3
related, web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2024-4536
advisory
-
github.com
/eclipse-edc/Connector
package
Sources
- CVE List CVE-2024-4536
- GitHub Advisory GHSA-2x52-8f29-7cjr
- NVD CVE-2024-4536
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.