Eclipse EDC Connector: Improper Authentication
CVE-2024-8642 is a high-severity improper authentication vulnerability in Eclipse EDC Connector from Eclipse Foundation, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 0.9.0 as the first without the flaw, so updating Eclipse EDC Connector to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.41% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Eclipse EDC Connector to 0.9.0 or a later version.
- Update edc to 0.9.0 or a later version.
- Update Eclipse Dataspace Components to 0.9.0 or a later version.
- Read the advisory on gitlab.eclipse.org for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Eclipse Foundation | Eclipse EDC Connector | 0.5.0 up to, but not including, 0.9.0 | 0.9.0 |
| Eclipse Foundation | edc | 0.5.0 up to, but not including, 0.9.0 | 0.9.0 |
| Eclipse | Eclipse Dataspace Components | 0.5.0 up to, but not including, 0.9.0 | 0.9.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 5.1 | Medium | CNA (eclipse.org) |
| CVSS 3.1 | 8.1 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
- gitlab.eclipse.org/security/cve-assignement/-/issues/28Issue Tracking
Recent Improper Authentication vulnerabilities
- 7.8 High severity
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 8.1 High severity
Spotted an error? Tell us.