CVE-2024-4536 (GCVE-0-2024-4536)
Vulnerability from cvelistv5
Published
2024-05-07 13:11
Modified
2024-08-01 20:40
Severity ?
VLAI Severity ?
EPSS score ?
CWE
Summary
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
| URL | Tags | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
Impacted products
| Vendor | Product | Version | ||
|---|---|---|---|---|
| Eclipse Foundation | EDC |
Version: 0.2.1 ≤ 0.6.2 |
{
"containers": {
"adp": [
{
"affected": [
{
"cpes": [
"cpe:2.3:a:eclipse_foundation:edc:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "edc",
"vendor": "eclipse_foundation",
"versions": [
{
"status": "affected",
"version": "0.2.1"
}
]
}
],
"metrics": [
{
"other": {
"content": {
"id": "CVE-2024-4536",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-05-07T14:50:50.630941Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2024-06-04T17:53:35.014Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
},
{
"providerMetadata": {
"dateUpdated": "2024-08-01T20:40:47.492Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"tags": [
"patch",
"x_transferred"
],
"url": "https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b"
},
{
"tags": [
"related",
"x_transferred"
],
"url": "https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3"
},
{
"tags": [
"issue-tracking",
"vendor-advisory",
"x_transferred"
],
"url": "https://gitlab.eclipse.org/security/cve-assignement/-/issues/22"
},
{
"tags": [
"issue-tracking",
"vendor-advisory",
"x_transferred"
],
"url": "https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"modules": [
"Connector"
],
"packageName": "technology.edc",
"product": "EDC",
"repo": "https://github.com/eclipse-edc/Connector",
"vendor": "Eclipse Foundation",
"versions": [
{
"lessThanOrEqual": "0.6.2",
"status": "affected",
"version": "0.2.1",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "sovity GmbH"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cdiv\u003eIn Eclipse Dataspace Components from version 0.2.1 to 0.6.2, in the EDC Connector component (\u003ca target=\"_blank\" rel=\"nofollow\" href=\"https://github.com/eclipse-edc/Connector\"\u003ehttps://github.com/eclipse-edc/Connector\u003c/a\u003e), an attacker might obtain OAuth2 client secrets from the vault.\u003c/div\u003e\u003cdiv\u003e\u003cbr\u003e\u003c/div\u003e\u003cdiv\u003e\u003cp\u003eIn Eclipse Dataspace Components from version 0.2.1 to 0.6.2, we have identified a security vulnerability in the EDC Connector component (\u003ca target=\"_blank\" rel=\"nofollow\" href=\"https://github.com/eclipse-edc/Connector\"\u003ehttps://github.com/eclipse-edc/Connector\u003c/a\u003e) 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\u0027s vault, not the consumer. This secret\u0027s 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.\u003c/p\u003e\n\u003cp\u003eThis feature is now disabled entirely, because not all code paths necessary for a successful realization were fully implemented.\u003c/p\u003e\u003cbr\u003e\u003c/div\u003e\u003cbr\u003e"
}
],
"value": "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\u0027s vault, not the consumer. This secret\u0027s 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"
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "ADJACENT_NETWORK",
"availabilityImpact": "LOW",
"baseScore": 6.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "LOW",
"privilegesRequired": "HIGH",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-201",
"description": "CWE-201: Insertion of Sensitive Information Into Sent Data",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-522",
"description": "CWE-522: Insufficiently Protected Credentials",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2024-05-07T13:11:45.310Z",
"orgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c",
"shortName": "eclipse"
},
"references": [
{
"tags": [
"patch"
],
"url": "https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b"
},
{
"tags": [
"related"
],
"url": "https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3"
},
{
"tags": [
"issue-tracking",
"vendor-advisory"
],
"url": "https://gitlab.eclipse.org/security/cve-assignement/-/issues/22"
},
{
"tags": [
"issue-tracking",
"vendor-advisory"
],
"url": "https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Eclipse EDC: OAuth2 Credential Exfiltration Vulnerability",
"x_generator": {
"engine": "Vulnogram 0.1.0-dev"
}
}
},
"cveMetadata": {
"assignerOrgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c",
"assignerShortName": "eclipse",
"cveId": "CVE-2024-4536",
"datePublished": "2024-05-07T13:11:45.310Z",
"dateReserved": "2024-05-06T07:05:31.518Z",
"dateUpdated": "2024-08-01T20:40:47.492Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"vulnerability-lookup:meta": {
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b\", \"tags\": [\"patch\", \"x_transferred\"]}, {\"url\": \"https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3\", \"tags\": [\"related\", \"x_transferred\"]}, {\"url\": \"https://gitlab.eclipse.org/security/cve-assignement/-/issues/22\", \"tags\": [\"issue-tracking\", \"vendor-advisory\", \"x_transferred\"]}, {\"url\": \"https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198\", \"tags\": [\"issue-tracking\", \"vendor-advisory\", \"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-01T20:40:47.492Z\"}}, {\"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-4536\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-05-07T14:50:50.630941Z\"}}}], \"affected\": [{\"cpes\": [\"cpe:2.3:a:eclipse_foundation:edc:*:*:*:*:*:*:*:*\"], \"vendor\": \"eclipse_foundation\", \"product\": \"edc\", \"versions\": [{\"status\": \"affected\", \"version\": \"0.2.1\"}], \"defaultStatus\": \"unknown\"}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-05-07T14:57:50.407Z\"}, \"title\": \"CISA ADP Vulnrichment\"}], \"cna\": {\"title\": \"Eclipse EDC: OAuth2 Credential Exfiltration Vulnerability\", \"source\": {\"discovery\": \"UNKNOWN\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"finder\", \"value\": \"sovity GmbH\"}], \"metrics\": [{\"format\": \"CVSS\", \"cvssV3_1\": {\"scope\": \"CHANGED\", \"version\": \"3.1\", \"baseScore\": 6.8, \"attackVector\": \"ADJACENT_NETWORK\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L\", \"integrityImpact\": \"LOW\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"HIGH\", \"availabilityImpact\": \"LOW\", \"privilegesRequired\": \"HIGH\", \"confidentialityImpact\": \"HIGH\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"repo\": \"https://github.com/eclipse-edc/Connector\", \"vendor\": \"Eclipse Foundation\", \"modules\": [\"Connector\"], \"product\": \"EDC\", \"versions\": [{\"status\": \"affected\", \"version\": \"0.2.1\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"0.6.2\"}], \"packageName\": \"technology.edc\", \"defaultStatus\": \"unaffected\"}], \"references\": [{\"url\": \"https://github.com/eclipse-edc/Connector/commit/a4e6018d2c0457fba6f672fafa6c590513c45d1b\", \"tags\": [\"patch\"]}, {\"url\": \"https://github.com/eclipse-edc/Connector/releases/tag/v0.6.3\", \"tags\": [\"related\"]}, {\"url\": \"https://gitlab.eclipse.org/security/cve-assignement/-/issues/22\", \"tags\": [\"issue-tracking\", \"vendor-advisory\"]}, {\"url\": \"https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/198\", \"tags\": [\"issue-tracking\", \"vendor-advisory\"]}], \"x_generator\": {\"engine\": \"Vulnogram 0.1.0-dev\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"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\u0027s vault, not the consumer. This secret\u0027s 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\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cdiv\u003eIn Eclipse Dataspace Components from version 0.2.1 to 0.6.2, in the EDC Connector component (\u003ca target=\\\"_blank\\\" rel=\\\"nofollow\\\" href=\\\"https://github.com/eclipse-edc/Connector\\\"\u003ehttps://github.com/eclipse-edc/Connector\u003c/a\u003e), an attacker might obtain OAuth2 client secrets from the vault.\u003c/div\u003e\u003cdiv\u003e\u003cbr\u003e\u003c/div\u003e\u003cdiv\u003e\u003cp\u003eIn Eclipse Dataspace Components from version 0.2.1 to 0.6.2, we have identified a security vulnerability in the EDC Connector component (\u003ca target=\\\"_blank\\\" rel=\\\"nofollow\\\" href=\\\"https://github.com/eclipse-edc/Connector\\\"\u003ehttps://github.com/eclipse-edc/Connector\u003c/a\u003e) 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\u0027s vault, not the consumer. This secret\u0027s 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.\u003c/p\u003e\\n\u003cp\u003eThis feature is now disabled entirely, because not all code paths necessary for a successful realization were fully implemented.\u003c/p\u003e\u003cbr\u003e\u003c/div\u003e\u003cbr\u003e\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-201\", \"description\": \"CWE-201: Insertion of Sensitive Information Into Sent Data\"}]}, {\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-522\", \"description\": \"CWE-522: Insufficiently Protected Credentials\"}]}], \"providerMetadata\": {\"orgId\": \"e51fbebd-6053-4e49-959f-1b94eeb69a2c\", \"shortName\": \"eclipse\", \"dateUpdated\": \"2024-05-07T13:11:45.310Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2024-4536\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-08-01T20:40:47.492Z\", \"dateReserved\": \"2024-05-06T07:05:31.518Z\", \"assignerOrgId\": \"e51fbebd-6053-4e49-959f-1b94eeb69a2c\", \"datePublished\": \"2024-05-07T13:11:45.310Z\", \"assignerShortName\": \"eclipse\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.1"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…