Eclipse BaSyx Go Components vulnerabilities
3 known vulnerabilities in Eclipse BaSyx Go Components from Eclipse Foundation. 3 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.1 High severity
Eclipse BaSyx Go Components: Exposure of Sensitive Information to an Unauthorized Actor
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
- 7.1 High severity
Eclipse BaSyx Go Components: Exposure of Sensitive Information to an Unauthorized Actor
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 fi
- 9.8 Critical severity
Eclipse BaSyx Go Components: Incorrect Behavior Order: Validate Before Canonicalize
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 configuratio