In Eclipse BaSyx Go Components versions up to and including 1.1.3, ABAC-enabled deployments match ROUTE access rules against the fully decoded request path, while the router routes on the raw, still encoded path. An encoded slash (%2F) inside a path value is a segment separator f...
Product
Eclipse Foundation Eclipse BaSyx Go Components vulnerabilities
4 published CVES affecting Eclipse Foundation Eclipse BaSyx Go Components, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 4
- Critical
- 1
- High
- 2
- Medium
- 1
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest Eclipse Foundation Eclipse BaSyx Go Components CVEs
Newest publication first
-
MediumCVSS 6.0 EPSS 0.29%
-
HighCVSS 7.1 EPSS 0.31%
In Eclipse BaSyx Go Components versions up to and including 1.1.2, ABAC-enabled deployments of the Submodel Repository and the AAS Environment return Submodel Elements that the caller is not authorized to read from GET /submodels/{submodelIdentifier}/submodel-elements. If an acce...
-
HighCVSS 7.1 EPSS 0.25%
In Eclipse BaSyx Go Components versions up to and including 1.1.2, ABAC-enabled deployments of the Submodel Repository and the AAS Environment do not apply an access rule's FILTERLIST fragment filters to single Submodel reads. GET /submodels removes the fields that a rule's FILTE...
-
CriticalCVSS 9.8 EPSS 0.46%
In Eclipse BaSyx Go Components versions up to and including 1.0.0, ABAC-enabled deployments are vulnerable to an authorization bypass caused by inconsistent trailing-slash handling between the ABAC middleware and the HTTP router. The shared router configuration used Chi's middlew...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.