{"answers":{"affected":"2 open source packages ship an affected version, including org.eclipse.edc:connector-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-4536 in the wild and no public exploit code.","fix":"Upgrade org.eclipse.edc:connector-core to 0.6.3 or later.","what":"CVE-2024-4536 is a medium-severity vulnerability in Eclipse Foundation EDC, published on 7 May 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-4536 and fix it if it is affected.\n\nWhat it is: CVE-2024-4536 is a medium-severity vulnerability in Eclipse Foundation EDC, published on 7 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-4536 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.eclipse.edc:connector-core (Maven): affected from 0.2.1; fixed in 0.6.3\n- org.eclipse.edc:connector-core (Maven): affected from 0.2.1; fixed in 0.6.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-4536/ (Markdown: https://insights.sbomify.com/CVE-2024-4536/index.md)","id":"CVE-2024-4536","markdown":"https://insights.sbomify.com/CVE-2024-4536/index.md","name":"CVE-2024-4536","record":{"aliases":["GHSA-2x52-8f29-7cjr"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Eclipse EDC Connector","requires_auth":"high_privilege","summary":"Attackers can exfiltrate OAuth2 client secrets from the provider's vault by exploiting a misconfigured data sink resolution context in Eclipse EDC.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"edc_connector","vendor":"eclipse"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Eclipse EDC: OAuth2 Credential Exfiltration Vulnerability","id":"CVE-2024-4536","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":4,"next":{"headline":"IDOR vulnerability in Janto Ticketing Software","id":"CVE-2024-4537"},"packages":[{"ecosystem":"Maven","fixed":["0.6.3"],"introduced":["0.2.1"],"last_affected":[],"package":"org.eclipse.edc:connector-core","purl":null,"source":"GHSA-2x52-8f29-7cjr"},{"ecosystem":"Maven","fixed":["0.6.3"],"introduced":["0.2.1"],"last_affected":[],"package":"org.eclipse.edc:connector-core","purl":"pkg:maven/org.eclipse.edc/connector-core","source":"GHSA-2x52-8f29-7cjr"}],"prev":{"headline":"KKProgressbar2 Free \u003c= 1.1.4.2 - Progress Bar Deletion via CSRF","id":"CVE-2024-4535"},"products":["EDC"],"published":"2024-05-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["Eclipse Foundation"]},"summary":"Attackers can exfiltrate OAuth2 client secrets from the provider's vault by exploiting a misconfigured data sink resolution context in Eclipse EDC.","url":"https://insights.sbomify.com/CVE-2024-4536/"}