Summary
Rainbond contains a broken access control vulnerability in its CheckToken function that can let an authenticated attacker access resources belonging to another enterprise.
By substituting an enterprise tenant name in URL paths while using a valid API token, an attacker may bypass enterprise ownership checks and access or modify protected platform resources.
Affected context
The issue occurs in Rainbond deployments where API requests use the CheckToken function to authorize access to enterprise-scoped resources. It becomes risky when enterprise identity is derived from a user-controlled URL path and is not consistently verified against the authenticated token's authorized enterprise. Affected resources may include services, plugins, environment variables, and certificates.
Exploit preconditions
- Attack surface: Authenticated Rainbond API endpoints handling enterprise-scoped resources
- Required access: Any valid API token accepted by the platform
- Trigger point: A request containing a substituted tenant or enterprise name in its URL path
- Why exploitation is possible: Authorization checks do not reliably bind the requested enterprise identifier to the enterprise associated with the authenticated principal
Why this happens
The underlying bug is an object-level authorization failure in which the application trusts an enterprise identifier supplied through a request path without enforcing server-side ownership checks.
This maps to CWE-639: Authorization Bypass Through User-Controlled Key, because a user-controlled key selects an enterprise-scoped object and the authorization decision does not adequately verify that the requester is permitted to access that object. Authentication confirms that a token is valid, but it does not by itself establish authorization for every enterprise resource named in the request.
Potential impact
- An authenticated attacker may read another enterprise's services or configuration
- An attacker could modify services, plugins, environment variables, or certificates
- Cross-tenant data exposure may occur
- Application behavior or deployment integrity could be disrupted
- Compromised configuration or certificates could support further attacks
General mitigation guidance
Mitigation typically focuses on enforcing authorization at the resource boundary rather than trusting identifiers supplied by clients.
Common defensive patterns include:
- Bind every enterprise-scoped request to the enterprise identity and permissions in the authenticated session or token
- Perform server-side object-level authorization checks for every read and write operation
- Avoid using URL tenant names as the sole basis for authorization decisions
- Apply deny-by-default policies when enterprise ownership cannot be established
- Limit tokens to the minimum enterprise scope and privilege required
- Use separate service identities and narrowly scoped permissions for administrative operations
How teams detect issues like this
Organizations commonly detect this class of issue through:
- Static analysis and code review checks for authorization decisions based only on URL, query, or body identifiers
- Review of authentication middleware and downstream resource authorization boundaries
- API tests that compare access to same-enterprise and cross-enterprise object identifiers
- Audit-log rules for a principal requesting resources across multiple enterprise scopes
- Policy enforcement requiring object-level authorization for every enterprise-scoped endpoint
Automated security testing and code review tools can help identify inconsistent tenant binding and missing authorization checks.

