6.8
MEDIUM
CVE-2024-4536
Eclipse Dataspace Components OAuth2 Client Secret Disclosure 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. 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.

INFO

Published Date :

May 7, 2024, 1:15 p.m.

Last Modified :

Feb. 6, 2025, 5:32 p.m.

Remotely Exploitable :

No

Impact Score :

5.3

Exploitability Score :

1.0
Affected Products

The following products are affected by CVE-2024-4536 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Eclipse edc_connector

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2024-4536 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2024-4536 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Feb. 06, 2025

    Action Type Old Value New Value
    Added CVSS V3.1 NIST AV:A/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:L
    Added CWE NIST CWE-522
    Added CPE Configuration OR *cpe:2.3:a:eclipse:edc_connector:*:*:*:*:*:*:*:* versions from (including) 0.2.1 up to (excluding) 0.6.3
    Changed Reference Type https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b No Types Assigned https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b Patch
    Changed Reference Type https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b No Types Assigned https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b Patch
    Changed Reference Type https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3 No Types Assigned https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3 Release Notes
    Changed Reference Type https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3 No Types Assigned https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3 Release Notes
    Changed Reference Type https://gitlab.eclipse.org/security/cve-assignement/-/issues/22 No Types Assigned https://gitlab.eclipse.org/security/cve-assignement/-/issues/22 Issue Tracking, Vendor Advisory
    Changed Reference Type https://gitlab.eclipse.org/security/cve-assignement/-/issues/22 No Types Assigned https://gitlab.eclipse.org/security/cve-assignement/-/issues/22 Issue Tracking, Vendor Advisory
    Changed Reference Type https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198 No Types Assigned https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198 Issue Tracking, Vendor Advisory
    Changed Reference Type https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198 No Types Assigned https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198 Issue Tracking, Vendor Advisory
  • CVE Modified by af854a3a-2127-422b-91ae-364da2661108

    Nov. 21, 2024

    Action Type Old Value New Value
    Added Reference https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b
    Added Reference https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3
    Added Reference https://gitlab.eclipse.org/security/cve-assignement/-/issues/22
    Added Reference https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198
  • CVE Modified by [email protected]

    May. 14, 2024

    Action Type Old Value New Value
  • CVE Received by [email protected]

    May. 07, 2024

    Action Type Old Value New Value
    Added 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.
    Added Reference Eclipse Foundation https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b [No types assigned]
    Added Reference Eclipse Foundation https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3 [No types assigned]
    Added Reference Eclipse Foundation https://gitlab.eclipse.org/security/cve-assignement/-/issues/22 [No types assigned]
    Added Reference Eclipse Foundation https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198 [No types assigned]
    Added CWE Eclipse Foundation CWE-522
    Added CWE Eclipse Foundation CWE-201
    Added CVSS V3.1 Eclipse Foundation AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2024-4536 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2024-4536 weaknesses.

CAPEC-12: Choosing Message Identifier Choosing Message Identifier CAPEC-217: Exploiting Incorrectly Configured SSL/TLS Exploiting Incorrectly Configured SSL/TLS CAPEC-612: WiFi MAC Address Tracking WiFi MAC Address Tracking CAPEC-613: WiFi SSID Tracking WiFi SSID Tracking CAPEC-618: Cellular Broadcast Message Request Cellular Broadcast Message Request CAPEC-619: Signal Strength Tracking Signal Strength Tracking CAPEC-621: Analysis of Packet Timing and Sizes Analysis of Packet Timing and Sizes CAPEC-622: Electromagnetic Side-Channel Attack Electromagnetic Side-Channel Attack CAPEC-623: Compromising Emanations Attack Compromising Emanations Attack CAPEC-50: Password Recovery Exploitation Password Recovery Exploitation CAPEC-102: Session Sidejacking Session Sidejacking CAPEC-474: Signature Spoofing by Key Theft Signature Spoofing by Key Theft CAPEC-509: Kerberoasting Kerberoasting CAPEC-551: Modify Existing Service Modify Existing Service CAPEC-555: Remote Services with Stolen Credentials Remote Services with Stolen Credentials CAPEC-560: Use of Known Domain Credentials Use of Known Domain Credentials CAPEC-561: Windows Admin Shares with Stolen Credentials Windows Admin Shares with Stolen Credentials CAPEC-600: Credential Stuffing Credential Stuffing CAPEC-644: Use of Captured Hashes (Pass The Hash) Use of Captured Hashes (Pass The Hash) CAPEC-645: Use of Captured Tickets (Pass The Ticket) Use of Captured Tickets (Pass The Ticket) CAPEC-652: Use of Known Kerberos Credentials Use of Known Kerberos Credentials CAPEC-653: Use of Known Operating System Credentials Use of Known Operating System Credentials
CVSS31 - Vulnerability Scoring System
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality
Integrity
Availability