EDC DataSetResolver policy filtering
The Eclipse Foundation is a Common Vulnerabilities and Exposures (CVE) Numbering Authority. This issue it used to request and track the progress of the assignment of a CVE for a vulnerability in the project code for an Eclipse open source project.
Basic information
Project name: Eclipse Dataspace Components (EDC)
Project id: technology.edc
Request type: publication
Versions affected: EDC versions from [0.1.3, 0.9.0] and fixed for versions >= 0.9.1
Common Vulnerability Scoring System: We rate the vulnerability as 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/E:U/RE:M/U:Amber, see {cvss}
Summary:
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. However, 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.
This 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.
Affected code: DatasetResolverImpl, L76-79
Links:
Tracking
This section will completed by the project team.
-
Reserve an entry only -
We're ready for this issue to be reported to the central authority (i.e., make this public now) -
(when applicable) The GitHub Security Advisory is ready to be published now
Note that for those projects that host their repositories on GitHub, the use of GitHub Security Advisories is recommended but is not required.
This section will be completed by the EMO.
CVE: {cve}
-
All required information is provided -
CVE Assigned -
Pushed to Mitre -
Accepted by Mitre