Eclipse Dataspace Components's ConsumerPullTransferTokenValidationApiController doesn't check for token validit

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.1 · CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:L/U:Green · score source

EPSS

• CVE-2024-8642: 0.41% estimated exploitation activity in the next 30 days; percentile 34.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

11 Sep 2024, 15:31 UTC

Last modified by the source

2 Feb 2026, 15:37 UTC

Source last checked

26 Oct 2026, 16:44 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8259-2x72-2gvc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-8642

Advisory: Eclipse Dataspace Components's ConsumerPullTransferTokenValidationApiController doesn't check for token validit
IDs: CVE-2024-8642, GHSA-8259-2x72-2gvc
Record: https://patchnext.com/advisories/cve-2024-8642 (revision 1, source checked 26 Oct 2026, 16:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.eclipse.edc:transfer-data-plane 0.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.eclipse.edc:transfer-data-plane: affected >= 0.5.0, < 0.9.0; fixed in 0.9.0

## Suggested inspection (read-only)
- Maven org.eclipse.edc:transfer-data-plane: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.eclipse.edc:transfer-data-plane.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8259-2x72-2gvc (GitHub-reviewed advisory GHSA-8259-2x72-2gvc lists affected ranges: Maven org.eclipse.edc:transfer-data-plane >=0.5.0 <0.9.0)

Commands are suggestions: review each one before running it.