Description
SurrealDB before 3.3.0 allows cross-tenant access because the SurrealQL USE statement switches a session to any namespace/database without checking that the caller's authenticated level covers it. Authenticated namespace, database, or record users can switch to another tenant and read, create, update, or delete rows in tables whose PERMISSIONS allow it, such as PERMISSIONS FULL.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| surrealdb | surrealdb | < 3.3.0 | 3.3.0 |
References
- GitHub Security Advisory (GHSA-2v9j-645m-pcrq) vendor-advisory
- VulnCheck Advisory: SurrealDB before 3.3.0 Cross-Tenant Access via USE Statement third-party-advisory