Horizon Alert
Summary of the vulnerability and why it matters
A security vulnerability has been identified in the Yuxi platform, affecting how it isolates different users' operational environments. This flaw allows a low-privileged user to access or alter data and operations belonging to other users, and potentially compromise shared internal services, leading to data disclosure, modification, or denial of service.
- Tenant data and operations are not properly isolated.
- Allows unauthorized access and control over other tenants.
- Confirm Yuxi relevance and assess potential exposure.
Attack Path
How an attacker could exploit the issue
An attacker with low-level access to the Yuxi platform can exploit a flaw in how Docker sandboxes are isolated. By executing commands within their own sandbox, they can access other tenants' data and functions, potentially disrupting services or stealing sensitive information. This can occur without needing administrator privileges or knowing specific credentials for backend systems like databases.
- Low-privileged authenticated user needed.
- Sandbox isolation bypass allows API access.
- Cross-tenant data compromise and DoS risk.
Live Threat
Current exploitation, exposure, and threat context
A low-privileged authenticated user could exploit insufficient isolation between Docker sandboxes and trusted application services. This could allow them to access other tenants' sandbox APIs, files, and secrets, execute commands in active sandboxes, or manage sandboxes. Furthermore, sandboxes could interact with shared internal services, potentially leading to command execution within a PostgreSQL container if default credentials are not changed and the exposed account is a superuser. These actions may result in disclosure or modification of cross-tenant data and sandbox states, or denial of service through sandbox deletion.
- Cross-tenant data and sandbox state.
- Access other tenants' sandbox APIs.
- Disclosure, modification, or denial of service.
Operational Fix
Recommended remediation, mitigation, and detection steps
Teams responsible for the Yuxi platform, including application owners and infrastructure or platform teams, must act. The immediate practical step is to identify all Yuxi deployments, assess their reachability and criticality, and pinpoint the accountable owners. Remediation planning should then be risk-based, considering the need to rotate default credentials for associated services like PostgreSQL, Neo4j, or MinIO.
- Platform and application teams own this.
- Verify all Yuxi instances and reachability.
- Rotate default credentials for related services.
