{"id":"CVE-2024-4536","aliases":["EUVD-2024-1371","GHSA-2x52-8f29-7cjr"],"status":"published","title":"Eclipse EDC: OAuth2 Credential Exfiltration Vulnerability","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.","severity":{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00411,"percentile":0.35688,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-201","CWE-522"],"published":"2024-05-07T13:11:45Z","modified":"2026-10-28T10:51:24Z","fixes":[{"ecosystem":"Maven","package":"org.eclipse.edc:connector-core","fixed_in":["0.6.3"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"org.eclipse.edc:connector-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.2.1"},{"fixed":"0.6.3"}]}]},{"source":"osv","ecosystem":"Maven","package":"org.eclipse.edc:connector-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.2.1"},{"fixed":"0.6.3"}]}],"versions":["0.2.1","0.3.0","0.3.1","0.4.0","0.4.1","0.5.0","0.5.1","0.6.0","0.6.1","0.6.2"]}],"products":[{"vendor":"eclipse","product":"edc_connector"},{"vendor":"eclipse foundation","product":"edc"},{"vendor":"eclipse_foundation","product":"edc"}],"references":[{"url":"https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b","tags":["patch","x_transferred","Patch","fix","web"]},{"url":"https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3","tags":["related","x_transferred","Release Notes","web"]},{"url":"https://gitlab.eclipse.org/security/cve-assignement/-/issues/22","tags":["issue-tracking","vendor-advisory","x_transferred","Issue Tracking","Vendor Advisory","report","web"]},{"url":"https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198","tags":["issue-tracking","vendor-advisory","x_transferred","Issue Tracking","Vendor Advisory","report","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-4536","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-2x52-8f29-7cjr"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/4xxx/CVE-2024-4536.json","tags":["advisory"]},{"url":"https://github.com/eclipse-edc/Connector","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2024-4536","title":"Eclipse EDC: OAuth2 Credential Exfiltration Vulnerability","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","status":"published","published":"2024-05-07T13:11:45.31Z","modified":"2024-08-01T20:40:47.492Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L","level":"medium","assessor":"cna"}],"cwes":["CWE-201","CWE-522"],"updated_at":"2026-11-02T14:34:16.78507Z"}],"euvd":[{"id":"EUVD-2024-1371","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","status":"published","published":"2024-05-07T13:11:45Z","modified":"2024-08-01T20:40:47Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L","level":"medium"}],"updated_at":"2026-11-03T03:50:36.775345Z"}],"ghsa":[{"id":"GHSA-2x52-8f29-7cjr","title":"Eclipse Dataspace Components vulnerable to OAuth2 client secret disclosure","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.","status":"published","published":"2024-05-07T15:30:36Z","modified":"2025-02-06T19:33:46Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L","level":"medium"}],"cwes":["CWE-201","CWE-522"],"updated_at":"2026-11-02T14:38:29.866763Z"}],"nvd":[{"id":"CVE-2024-4536","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","status":"published","published":"2024-05-07T13:15:48.513Z","modified":"2026-06-17T08:02:05.68Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L","level":"medium","assessor":"secondary"},{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:L","level":"medium","assessor":"primary"}],"cwes":["CWE-201","CWE-522"],"updated_at":"2026-11-02T14:09:57.497105Z"}],"osv":[{"id":"CVE-2024-4536","title":"Eclipse EDC: OAuth2 Credential Exfiltration Vulnerability","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","status":"published","published":"2024-05-07T13:11:45.31Z","modified":"2026-10-28T10:51:24.166615651Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L","level":"medium"}],"cwes":["CWE-201","CWE-522"],"updated_at":"2026-11-02T15:44:42.790566Z"},{"id":"GHSA-2x52-8f29-7cjr","title":"Eclipse Dataspace Components vulnerable to OAuth2 client secret disclosure","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.","status":"published","published":"2024-05-07T15:30:36Z","modified":"2025-02-06T19:49:31.84427Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L","level":"medium"}],"cwes":["CWE-201","CWE-522"],"updated_at":"2026-11-02T15:46:35.050232Z"}]}}