# CVE-2024-4536: Eclipse EDC: OAuth2 Credential Exfiltration Vulnerability > Attackers can exfiltrate OAuth2 client secrets from the provider's vault by exploiting a misconfigured data sink resolution context in Eclipse EDC. - **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 May 2024 - **Updated:** 1 Aug 2024 - **Also known as:** GHSA-2x52-8f29-7cjr ## What is CVE-2024-4536? CVE-2024-4536 is a medium-severity vulnerability in Eclipse Foundation EDC, published on 7 May 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official 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. Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-201 (Insertion of Sensitive Information Into Sent Data) ## Which versions are affected by CVE-2024-4536? 2 open source packages ship an affected version, including org.eclipse.edc:connector-core. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.eclipse.edc:connector-core` | Maven | From 0.2.1 | 0.6.3 | | `org.eclipse.edc:connector-core` | Maven | From 0.2.1 | 0.6.3 | Products: Eclipse Edc Connector. ## How do I fix CVE-2024-4536? Upgrade org.eclipse.edc:connector-core to 0.6.3 or later. ## Is CVE-2024-4536 being exploited? There is no known exploitation of CVE-2024-4536 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-4536 and fix it if it is affected. What it is: CVE-2024-4536 is a medium-severity vulnerability in Eclipse Foundation EDC, published on 7 May 2024. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-4536 in the wild and no public exploit code. Affected packages and fixed versions: - org.eclipse.edc:connector-core (Maven): affected from 0.2.1; fixed in 0.6.3 - org.eclipse.edc:connector-core (Maven): affected from 0.2.1; fixed in 0.6.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-4536/ (Markdown: https://insights.sbomify.com/CVE-2024-4536/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-4536 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-4536 - OSV: https://osv.dev/vulnerability/CVE-2024-4536 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-4536/ Summaries are generated and may contain mistakes; the official description above is the record.