Horizon Alert
Summary of the vulnerability and why it matters
This vulnerability in CubeSandbox could allow an authenticated user to gain unauthorized access to host file systems, potentially leading to the execution of arbitrary code and compromise of the underlying infrastructure. The issue stems from insufficient authorization checks when handling host path requests, allowing tenants to mount arbitrary directories into their sandboxed environments.
- Tenants can mount any host directory.
- This allows unauthorized host access and code execution.
- Confirm relevance and potential exposure.
Attack Path
How an attacker could exploit the issue
An attacker with authenticated access can exploit this vulnerability by sending a crafted request to the `/sandboxes` endpoint. This request allows them to specify an arbitrary host path within the `metadata["host-mount"]` field. The system then recursively binds this host path into the tenant's MicroVM, granting the attacker read-write access to host files, the ability to execute code on the host, and access to the container runtime.
- Authenticated access to the API.
- Supply arbitrary host path in request.
- Host file access and code execution.
Live Threat
Current exploitation, exposure, and threat context
An authenticated user with permission to create sandboxes could manipulate the `host-mount` metadata to include arbitrary host paths. This could allow them to recursively bind mount host directories into the sandbox with read-write access, potentially leading to unauthorized access and modification of host files, execution of arbitrary code on the host, or compromise of other tenants.
- Host file system data.
- Arbitrary host path supplied to API.
- Host compromise and data access.
Operational Fix
Recommended remediation, mitigation, and detection steps
In a real-world scenario, platform or infrastructure teams are likely responsible for CubeSandbox, as it manages AI agent sandboxes. The first actionable step is to identify all CubeSandbox instances, confirm their exposure and criticality, and then assign ownership to the accountable team for risk-based remediation planning.
- Platform or Infrastructure teams own this.
- Verify host-mount reachability and criticality.
- Plan and coordinate remediation actions.