In SAP/astonish, an authenticated user could potentially identify and operate on another team’s sandbox containers because of improper tenant isolation in the legacy Incus sandbox-management API handlers. The affected handlers did not use the tenant-aware session lookup path, allowing cross-tenant container operations such as listing, exposing or proxying, and deleting containers.
The issue affects only the legacy Incus backend. Kubernetes and OpenShell deployments are not affected because the relevant Incus-specific handlers are unavailable there.
PATCH DETAILS:
The fix routes the affected handlers through buildPGSessionRegistry() or an equivalent tenant check, ensuring proper session lookup scoping.
WORKAROUND:
No workaround available. Apply the patch by upgrading to the fixed version.
In SAP/astonish, an authenticated user could potentially identify and operate on another team’s sandbox containers because of improper tenant isolation in the legacy Incus sandbox-management API handlers. The affected handlers did not use the tenant-aware session lookup path, allowing cross-tenant container operations such as listing, exposing or proxying, and deleting containers.
The issue affects only the legacy Incus backend. Kubernetes and OpenShell deployments are not affected because the relevant Incus-specific handlers are unavailable there.
PATCH DETAILS:
The fix routes the affected handlers through buildPGSessionRegistry() or an equivalent tenant check, ensuring proper session lookup scoping.
WORKAROUND:
No workaround available. Apply the patch by upgrading to the fixed version.