CVE-2024-4536

Source
https://nvd.nist.gov/vuln/detail/CVE-2024-4536
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-4536.json
Aliases
Published
2024-05-07T13:15:48Z
Modified
2024-05-15T01:16:37.948158Z
Summary
[none]
Details

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.

References

Affected packages

Git / github.com/eclipse-edc/connector

Affected ranges

Type
GIT
Repo
https://github.com/eclipse-edc/connector
Events
Introduced
0The exact introduced commit is unknown
Fixed

Affected versions

Other

ion-hackathon
milestone-2
milestone-3
milestone-4

milestone-3.*

milestone-3.1

v0.*

v0.0.1-milestone-5
v0.0.1-milestone-6
v0.0.1-milestone-7
v0.0.1-milestone-8
v0.0.1-milestone-9
v0.1.0
v0.1.1
v0.1.2
v0.1.3
v0.2.0
v0.2.1
v0.3.0
v0.3.1
v0.4.0
v0.4.1
v0.5.0
v0.5.1
v0.6.0
v0.6.1
v0.6.2