{"id":"CVE-2024-4536","url":"https://www.cyber-defence.io/tools/cve/CVE-2024-4536","generatedAt":"2026-10-28T07:03:39.874Z","title":"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.","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.\n\nIn 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.\n\nThis feature is now disabled entirely, because not all code paths necessary for a successful realization were fully implemented.\n\n","published":"2024-05-07T13:15:49.000Z","lastModified":"2026-06-17T08:02:06.000Z","status":"Analyzed","sourceIdentifier":"emo@eclipse.org","cvss":{"version":"3.1","score":5.3,"severity":"MEDIUM","vector":"CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:L"},"cwe":["CWE-201","CWE-522"],"affected":["eclipse/edc connector"],"epss":{"score":0.00411,"percentile":0.35212,"date":"2026-10-27","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"low","text":"Lower severity and a low EPSS score (0.41%). Track it; it rarely justifies an emergency change on its own."},"changes":[],"references":[{"url":"https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b","tags":["Patch"],"source":"emo@eclipse.org"},{"url":"https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3","tags":["Release Notes"],"source":"emo@eclipse.org"},{"url":"https://gitlab.eclipse.org/security/cve-assignement/-/issues/22","tags":["Issue Tracking","Vendor Advisory"],"source":"emo@eclipse.org"},{"url":"https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198","tags":["Issue Tracking","Vendor Advisory"],"source":"emo@eclipse.org"},{"url":"https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b","tags":["Patch"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3","tags":["Release Notes"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://gitlab.eclipse.org/security/cve-assignement/-/issues/22","tags":["Issue Tracking","Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198","tags":["Issue Tracking","Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2024-4536","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}