Eclipse Dataspace Components vulnerabilitiesRanked by how likely they are to be used.
Eclipse Dataspace Components is made by Eclipse. We track 2 published vulnerabilities in it, across 24 versions. None of them is on the list of flaws known to be exploited today. If you run Eclipse Dataspace Components, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Eclipse Dataspace Components vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Eclipse Dataspace Components's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Eclipse Dataspace Components flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.4%CVE-2024-8642Medium
In Eclipse Dataspace Components, from version 0.5.0 and before version 0.9.0, the ConsumerPullTransferTokenValidationApiController does not check for token validity (expiry, not-before, issuance date), which can...
- 0.4%CVE-2024-9202Medium
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...
Running Eclipse Dataspace Components? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
In Eclipse Dataspace Components, from version 0.5.0 and before version 0.9.0, the ConsumerPullTransferTokenValidationApiController does not check for token validity (expiry, not-before, issuance date), which can allow an attacker to bypass the check for token expiration. The issue requires to have a dataplane configured to support http proxy consumer pull AND include the module "transfer-data-plane". The affected code was marked deprecated from the version 0.6.0 in favour of Dataplane Signaling. In 0.9.0 the vulnerable code has been removed.
- Matched to
- Eclipse Dataspace Components on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 2 published vulnerabilities listed under the name Eclipse Dataspace Components, across 24 versions.
None of Eclipse Dataspace Components's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Eclipse Dataspace Components. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.