{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-9202 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-9202 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-9202 is a medium-severity missing authorization vulnerability in Eclipse Dataspace Components, published on 27 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-9202 and fix it if it is affected.\n\nWhat it is: CVE-2024-9202 is a medium-severity missing authorization vulnerability in Eclipse Dataspace Components, published on 27 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-9202 in the wild and no public exploit code.\n\nAffected product: Eclipse Dataspace Components. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-9202/ (Markdown: https://insights.sbomify.com/CVE-2024-9202/index.md)","id":"CVE-2024-9202","markdown":"https://insights.sbomify.com/CVE-2024-9202/index.md","name":"CVE-2024-9202","record":{"aliases":["GHSA-78wc-gq29-f2pq"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Dataspace connector","requires_auth":"low_privilege","summary":"Attackers can view restricted datasets by guessing IDs due to missing policy filtering in the Eclipse Dataspace Components connector.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"eclipse_dataspace_components","vendor":"eclipse"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/RE:M/U:Amber","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"In Eclipse Dataspace Components versions 0.1.3 to 0.9.0, the Connector component filters which datasets (= data offers) another party can see in a requested catalog, to ensure that only authorized parties are able to view restricted offers.\nHowever, there is the possibility to request a single dataset, which should be subject to the same filtering process, but currently is missing the correct filtering.\n\nThis enables parties to potentially see datasets they should not have access to, thereby exposing sensitive information. Exploiting this vulnerability requires knowing the ID of a restricted dataset, but some IDs may be guessed by trying out many IDs in an automated way.\n\nAffected code:\n DatasetResolverImpl, L76-79 https://github.com/eclipse-edc/Connector/blob/v0.9.0/core/control-plane/control-plane-catalog/src/main/java/org/eclipse/edc/connector/controlplane/catalog/DatasetResolverImpl.java","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"EDC DataSetResolver policy filtering missing","id":"CVE-2024-9202","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Enpass Password Manager sensitive information in memory","id":"CVE-2024-9203"},"packages":[],"prev":{"headline":"SQL injection vulnerability in SEUR plugin","id":"CVE-2024-9201"},"products":["Eclipse Dataspace Components"],"published":"2024-09-27","related":[{"cvss_score":5,"headline":"Eclipse EDC: Consumer pull transfer token validation checks not applied","id":"CVE-2024-8642","kev_date_added":null,"published":"2024-09-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-27","vendors":["Eclipse Foundation"]},"summary":"Attackers can view restricted datasets by guessing IDs due to missing policy filtering in the Eclipse Dataspace Components connector.","url":"https://insights.sbomify.com/CVE-2024-9202/"}